Enable Sanitizers and Valgrind in GitHub Actions Workflows

[jr0me]

Description

To improve the robustness and reliability of the codebase, we need to integrate tools like AddressSanitizer, ThreadSanitizer, UndefinedBehaviorSanitizer, and Valgrind into our CI pipeline. These tools can help identify memory leaks, invalid accesses, race conditions, and undefined behavior during automated testing.

This task involves:

• Enabling sanitizers (e.g., AddressSanitizer, ThreadSanitizer) in the build process for specific workflows.
• Configuring Valgrind to run memory analysis tests.
• Updating GitHub Actions workflows to include these tools in the testing stages.
• Adding relevant checks and ensuring any issues detected are logged and reported clearly.

The goal is to catch critical bugs early in the development process, improving the overall quality and stability of the software.

[jr0me]

Update

Looking into enabling valgrind. Some "still reachable" warnings appear. Analyzing if they are problematic or not.