Adding a config option, automaticConfigReload, controlling the behaviour...

... of the config file reloading feature.

This adds a config option to disable the automatic config reloading feature. This feature is good, but can be operationally unpredictable. Ops/admins expect that changes made to a config file will not take effect until the service is restarted. Restarting a service (and possibly crashing it) when a half-complete config is saved (accidentally or out of habit) is surprising, and operations people hate surprises. :)

The default behaviour is not changed, most users won't notice or care.