Refactor and Move Interfaces, Types, and Enums into Separate Files

[saadanzari]

Description

Currently, interfaces, types, and enums are scattered throughout the codebase, making them harder to locate and maintain. These should be moved into separate, appropriately named files within component folders or a centralized folder. Loosely Coupled Code principle should be followed.

Acceptance Criteria

• Identify all interfaces, types, and enums in the codebase.
• Move these into separate files located within their respective component folders or a centralized /types or /interfaces directory based on Global types.
• Update all import paths in the codebase to reflect the new locations.
• Ensure the project builds successfully and passes type-checking after refactoring.
• Provide a guideline in the project documentation on where to define and locate interfaces, types, and enums.