Reporting module should not load reports from config automatically in activator

When we recently added the ability to load in reports from configuration files using the ReportLoader, this was setup to automatically load reports when the reporting module started.

However, there are situations where distributions might want finer-grained control over the exact timing of when reports are setup (eg. after other metadata has been loaded or conditionally depending on other implementation-defined variables).

This ticket is to introduce a change (that is not backwards compatible) that would introduce a global property to indicate if reports should be loaded automatically from configuraiton or not during reporting module startup, defaulting to false.

Any implementations currently relying on this ability (and the assumption is that there are very few outside of PIH since this is not a documented feature) would be able to retain the same capabilities in future upgrades without introducing any new code changes, but would need to set this global property to true to do so.

mogoodrich FYI