Bug 61009

With a static MPM, `httpd -V` will correctly print out the compiled settings, even if the configuration file is invalid or completely missing. With MPM DSOs, an invalid configuration will prevent the compiled settings from being printed, even if we know all of them.

An example I run into commonly is in normal HTTPS operation, where the private key is stored in a folder that's only accessible by the superuser. This prevents non-superusers from being able to run `httpd -V`... but only if they're using dynamic MPMs.

I don't think a configtest is ever appropriate during -V operation. Users who want a configtest can run a configtest. In the situation where we can figure out which MPM is in use during ap_read_config(), we should immediately print what we know and exit. Even if we can't read the configuration at all, we can print out the settings we *do* know, and mark the MPM as [unknown] or something.