Module logs version of libmodsecurity headers it was built against, not dynamically linked version

This is cosmetic, but since it had me scratching my head for a while I figured it's helpful to log as a bug.

In ngx_http_modsecurity_module.c:ngx_http_modsecurity_init_main_conf() the module emits an error log entry noting the number of rules loaded and the version of libmodsecurity3. The version number comes from constants which are derived from the header file modsecurity/modsecurity.h. https://github.com/owasp-modsecurity/ModSecurity-nginx/blob/9eb44fd9ab0988756e1ab8ce5aa5548ddbe57846/src/ngx_http_modsecurity_module.c#L691

These symbols are resolved at compile time from the header file, but the module itself is dynamically linked and so this may not reflect the version of the library in use by the module.

Practically, fixing this would require a new API in libmodsecurity to request the library version and calling that from the connector. This would not be a backward-compatible change and may not make sense outside of a significant update.

Start at src/ngx_http_modsecurity_module.c in ngx_http_modsecurity_init_main_conf() and inspect the version constants from modsecurity/modsecurity.h. Compare those compile-time values with what the dynamically linked library can expose, while reviewing the stated backward-compatibility constraint. Done means determining whether a runtime-version API and connector change can be scoped across the relevant projects.