Modularize settings

[maksis]

Having GUI and core module settings in the core is a bit messy (it should be possible for them to manage the settings separately instead)

[Night (night.)]

This would mean separating config items in the settings dialog also. I cant think of any nice way of doing this without always manually handling them separate in code and that seems even more messy.

[maksis (maksis)]

This is also related to extensions as they would be quite limited without the ability to add configurable settings in the UI. I've been thinking of the following format:

string key, string caption, string type ("int", "string", "bool", "text", "file_path", "directory_path", "size", "second", "minute", "speed"...), (int|string|bool) value

Very much like https://github.com/airdcpp/airgit/blob/master/airdcpp/airdcpp/SettingItem.h

It's not an issue for the Web UI to generate setting forms dynamically based on those definitions, possibly the Windows GUI would be able to do the same.