create new module cfg functionality

[ewerybody]

On the far end we don't want to touch the configurations manually but only through the interface. This calls for embedding all functionality in the interface in the first place. So there is never a difference of hidden and exposed functionality.

so the user will see the controls with the settings of a module read from the cfg
and when in 'dev mode': an option to change or add stuff, or option to create a module cfg with a list of provided files in the module.

...

[ewerybody]

Done.
the ui reads the config.json and builds "draw" controls from that. (currently that's only the nfo control)
editing creates a copy of the config as tempConfig and builds editable controls from that. While editing only the tempConfig is changed. On OK the tempConfig is submitted and a data refresh is initiated which rewrites the includes and calls the ahk runtime again.