[Refactor] Separate Build and Test in CMake

[pedrobiqua]

🎯 Reason for Refactoring

The current CMake setup mixes the build process with test execution, making the codebase less modular and harder to maintain. By refactoring, we aim to separate the build and test functionalities to improve organization, readability, and maintainability.

---

🔍 Current Code Description

• The current implementation combines the build and test logic within a single CMakeLists.txt file.
• Test targets (add_test) are defined alongside build targets, which makes it harder to manage and scale the project.
• There is no clear distinction between the code required for building the project and the code dedicated to testing.

---

✅ Proposed Solution

1. Create a dedicated tests/CMakeLists.txt file to handle all test-related targets and configurations.
2. Include the tests/CMakeLists.txt in the root CMakeLists.txt using add_subdirectory.
3. Separate test dependencies from build dependencies, ensuring clarity in the configuration.
4. Maintain a modular structure where the build system and test system can evolve independently.

---

📈 Expected Impact

• Improve project organization by clearly separating build and test logic.
• Make the project more modular, simplifying future feature additions and changes.
• Facilitate easier debugging and faster iteration during the testing process.
• Enhance collaboration among team members by providing a clearer structure.

---

🛠️ Completion Checklist

• Create a tests/CMakeLists.txt file and move all test-related configurations there.
• Update the root CMakeLists.txt to include the test directory using add_subdirectory.
• Verify that all build targets remain functional after refactoring.
• Ensure all tests run as expected after the refactor.
• Update documentation to reflect the new project structure.

---

📂 Related References

• CMake Documentation: [add_subdirectory](https://cmake.org/cmake/help/latest/command/add_subdirectory.html)
• Related issue: #123 (example reference)

---

💡 Additional Notes

This refactoring will make it easier to add new test suites or extend the testing framework in the future. Additionally, this separation aligns with industry best practices and prepares the project for potential CI/CD pipeline improvements.