ConfigurationManager should not be a micromanager #498
Description
ConfigurationManager should be able to manage configuration life cycle events without micromanaging!!
Jokes aside the task here to change the relationship between ConfigurationManager and the various processes and components configuration classes in a way that would allow ConfigurationManager to load and reload configurations without knowing the details of the individual components.
ConfigurationManager should be able to load and reload the configuration changes triggered by different events and signals, but it doesn't need to own the memory of those configuration blocks, or know their internal details. This would also allow us to change the details of individual modules configuration without the need to rebuild the other components.