Finer settings freezing control

[nickpharrison]

Description

I have a use-case where I would like to control which settings users can change. I share my instance with friends whom I trust (hence no authentication issues) but I do not want them to accidentally change certain settings.

The --freeze-settings parameter is not suitable because there are some settings which they should be able to change (such as the currently used checkpoint), and the --hide-ui-dir-config is only applicable for a small subset of settings (plus this setting as HIDES the settings completely, which I do not necessarily want to do.

The solution I suggest (and have implemented so far) is:

• allow users to use --freeze-settings to globally stop settings being changed
• otherwise, specify a list to UI "sections" where they can freeze whole tabs of settings from being edited (as defined in modules/shared_options.py). This can be done by specifying a comma-delimited list in the new command line option --freeze-settings-in-sections
• also allow users to prevent individual settings from being edited if they don't want to freeze. This can be done by specifying a comma-delimited list in the new command line option --freeze-specific-settings

The changes to the code add the two new options to the known commands list (in modules/cmd_args.py) and add additional assertions when setting new settings (in the same way as --freeze-settings does)

Example options for testing:

--freeze-settings-in-sections API,system --freeze-specific-settings samples_save

Screenshots/videos:

Checklist:

• I have read contributing wiki page
• I have performed a self-review of my own code
• My code follows the style guidelines
• My code passes tests

[AUTOMATIC1111]

you lost some settings/reverted some changes in modules/cmd_args.py.