Logging service shouldn't get started until it's fully read in the config files

[Russell Taylor]

At the moment, the logging starts up after the Mantid.properties file is read in, and before the Mantid.user.properties file has been read in.

This can lead to things like:

• Spurious messages about directories not existing, when in fact their about to be correctly set in the Mantid.user.properties.
• A file and/or directory for the log being created in the default place specified in the Mantid.properties file even though the Mantid.user.properties will override it.

[Russell Taylor]

(In [4160]) Downgrade some of the logging messages in the ConfigService - they weren't necessarily errors and could be confusing. Re #1161.

[Russell Taylor]

(In [4172]) Re-jig the ConfigService so that the logging doesn't start up until after the Mantid.user.properties file has been dealt with. Re #1161.

[Stuart Campbell]

This ticket has been transferred to github issue ​2009