Configuration should be JSON based in a $config object

[EdLichtman]

Instead of what I'm doing which is declaring the Configuration Settings in the Private Functions Help file, I should Generate the Configuration Settings in the Importing psm1 file. First I'll see if the Config file exists, and if it doesn't I'll create it. Then I'll Convert from JSON into an object, set the values and convert back to JSON.

The benefit of this is configuration will become Scalable. I'd like to make a variable "AutoLoadingPreference" to change whether the QuickModuleCLI AutoLoads, since I shouldn't dictate what other people's environments look like. If AutoLoadingPreference is set to None, then No functions get AutoLoaded. If AutoLoadingPreference is set to Nested, then there should also be a "AutoLoadingNestedModules" Array of Module Names that automatically gets added to when a new module is created. If AutoLoadingPreference is set to Module, then Only Module Functions are autoloaded. and if AutoLoading preference is set to All, then all Modules, Nested Modules will be autoloaded.

Then I'd have a
Set-AutoLoadingPreference command -AutoLoadingPreference -Modules

And I can look at dynamically generating the Values that can be stuck into the Modules.

This would open up to much more configuration changes too.