Refactor Project Structure and Clean Unused Libraries

[Romazes]

Description

This pull request aims to enhance the project by performing a comprehensive refactoring of the solution. The changes include renaming all projects within the solution, updating folder paths, and refining project names. Additionally, namespace modifications have been made for improved consistency and clarity. In the final step, any unused libraries across all files have been identified and removed to optimize the codebase.

Related Issue

N/A

Motivation and Context

The motivation behind this refactor is to establish a more organized and coherent project structure. By renaming projects and adjusting folder paths, the codebase becomes more intuitive and easier to navigate. Consistent naming conventions in namespaces contribute to better code readability and maintainability. The removal of unused libraries ensures a leaner project, reducing potential conflicts and enhancing overall performance.

Requires Documentation Change

N/A

How Has This Been Tested?

The changes have been thoroughly tested across various scenarios to ensure the refactoring does not introduce any regressions. Unit tests have been executed to validate the correctness of the code after the renaming and removal of unused libraries. Integration tests have been performed to guarantee the compatibility of the refactored code with the overall system. Manual testing was carried out to identify any potential issues not covered by automated tests. The project has been built and run successfully to confirm the stability of the updated codebase.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• Refactor (non-breaking change which improves implementation)
• Performance (non-breaking change which improves performance. Please add associated performance test and results)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Non-functional change (xml comments/documentation/etc)

Checklist:

• My code follows the code style of this project.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

[Martin-Molinero]

Thank you! 🚀