Additional Warning/Hardening Test in CI

[Easton97-Jens]

• I added a separate CI workflow/build job for ModSecurity v3 to make compiler warnings and hardening-related issues visible earlier in the development process.
• The job intentionally builds ModSecurity with stricter GCC warning flags such as -Wall, -Wextra, -Wformat, and -Wformat-security.
• The run currently operates in a warn-only mode so existing warnings become visible in CI without immediately failing the entire workflow because of -Werror.
• This helps detect potential issues and regressions early and allows them to be fixed proactively before they appear in Fedora/RHEL packaging or downstream builds.
• In addition, all relevant compiler, linker, and configure flags are printed in the CI logs to improve transparency and reproducibility of the build environment.
• The long-term goal is to continuously reduce warnings and hardening issues and eventually re-enable stricter error handling (-Werror).

#3567

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud