Support for read only server configuration directory

We need something like
--disable-configuration-history
to use when running in containers to avoid write to any directory ('standalone_xml_history').

History backups are senseless running on a container, and certain cloud use cases could require a non-writable storage mounted as a configuration directory. Also, when we are running on a non-containerized environment we could have very strict security rules that could force us the use of a read-only configuration directory.

We need a solution to make the server able to work with read-only configuration directories.