Config subsystem fails silently by default

In Lithium we have noticed that the config subsystem fails silently if a config file fails to be parsed, or if it fails to find services. Their is an uncaught exception that is ultimately printed to standard out, which should in theory be showing up in karaf.out (which is not where people look by default).

It would be nice if the config sub system can log 1) when it successfully parses a config file and 2) if there are any thrown exceptions reporting an error, log those to the karaf.log at a WARN or ERROR log (or even FATAL since it stops the controller dead in the water).