OP-182 Service to manage auto discovering configuration categories for the system config section
OP-182 refactoring the way in which config categories are auto discovered

Now based on i18n files in a conventional folder. No individual preside objects will be used as we will store all configuration values in a single db table
OP-182 Method to retrieve details of an individual configuration category
OP-162 Ability to save system config settings to the database
OP-182 using a better name for the saveConfig() method, saveSetting()
OP-182 Implementing getSetting()
OP-182 Refactoring data layer expected columns - do not use Preside Object 'label' field to represent the setting name - have 'setting' instead and do not have a label field at all
OP-182 Method to retrieve all settings for a given category
OP-182 Changing convention of how settings categories are discovered. Now uses preside forms rather than i18n bundles

i18n bundles are an optional part of the category, forms are a must
OP-182 Building system settings main menu based on configured categories
OP-182 rendering the edit form for a settings category
OP-182 a little robustness in the edit category handler
OP-182 Ability to save configuration form settings
OP-182 First draft documentation for global system settings
OP-292 Fixes for pathing issues on unix systems that prevented a Preside site from starting up
OP-182 Creating our own Preside DSL provider for wirebox and implementing a rough system settings injector

[skip-ci]
OP-182 A little more docuemtnation around using editable system settings in your service layer

[skip-ci]
OP-293 Using wirebox injection DSLs to wire up our service layer rather than manually wiring them in Wirebox.cfc

[skip-ci] This will, for now, completely break the tests
OP-293 Fixing invalid super class reference after refactoring service layer to not use super classes
OP-293 Fixing all the testcases that needed changing after refactored the way in which service layer interacts with Preside objects, etc.