Implement a uniform loading of Configurations throughout plugin

[davidmc971]

We currently have the issue that we write most command-specific configuration options and data into a single settings.yml and access that data through one shared object.
To improve on this we could load sections of configurations for use with different commands and modules and make those available separately as well as have separate config files for logically unrelated options and data.