settings(feat): reset to default value

[chipsTM]

adds #576

taking suggestions on css formatting and handling custom components/ignores

[chipsTM]

I was thinking that another property (disableReset ?) should be added to SettingNode interface so that a setting can be declared as non-resettable when one uses declareConfig. At least this way we can exclude custom types or types with non-primitive values?

[Melonify]

The behavior of this isn't quite right. Ideally it should remove the setting from the stored table entirely, so that if a setting's default value changes for some reason it's as if the user had never changed the setting.

Allowing the post-reset state to be separate from the initial state adds to potential user confusion.

[AnatoleAM]

Thank you for the contribution 🙂