Create config patching mechanism

[aggregate1166877]

Details:
If a new feature is created and is stored in the user profile, existing profiles never have the value set. Users have to manually delete their entire profile for all new values to make their way to the profile configs (or manually change items in menus to trigger a write of those specific items).

We need logic that specifically checks if any config values in user profile files are undefined (not null or falsy, actually undefined). If undefined, it should be patched and saved. This mechanism should not be version aware (unless we have an exceptional case). It should simply check for undefined config values and set them.

We might need to (at least partially) exclude controls from this however, because we do not want new features clashing with existing user control bindings. Instead, the user should have the option to reset individual new controls from blank to default, maybe even an option to automatically set all unbound controls to their defaults. In the latter case, the user should be given a list of controls that will be changed, with the option to cancel the auto-bind.