[BUG][DOCUMENTATION] Prevent new config opts being added to Salt without minimum reqs (ex. docs, VALID_OPTS, etc.)

[ScriptAutomate]

Is your feature request related to a problem? Please describe.

pre-commit needs to monitor the salt/config/__init__.py (and the conf/* files, and the conf rst files) for new opts/options added to Salt. There have been new options added at a pace faster than they've been documented. As a result, we have a mix of over 100 undocumented and underdocumented options for salt configs.

Before we start documenting everything that is undocumented/underdocumented, we need to prevent any new options from being added that aren't documented properly.

Describe the solution you'd like

• Create a document with proper guidance on adding a new opt to Salt configs:
  • VALID_OPTS
  • DEFAULT_*_OPTS
  • etc.
• pre-commit needs to monitor the salt/config/__init__.py (and the conf/* files, and the conf rst files)
• Whenever a new opt appears in salt/config/__init__.py that differs from what is currently there, we need to verify that:
  • Is the option properly documented in the conf/minion and/or conf/master?
  • Is the same option properly documented in the .rst equivelants, like doc/ref/configuration/minion.rst and/or doc/ref/configuration/master.rst?

Describe alternatives you've considered

I'm not quite sure what alternative paths there would be that could assist in preventing these from continuously growing the backlog.

Additional context

This is directly related to an EPIC issue and the PRs/issues linked within it: #58112

Please Note

Should require no SEP. I wasn't sure what type of issue this should be. This could be a mixture of bug, documentation, and feature request:

• bug: opts that are implemented in non-standard ways, so incredibly hard to audit what available opts there are
• documentation: There are ~100 undocumented/underdocumented options, as pointed out by [EPIC] Documented options in minion/master config files don't match minion/master config documentation, and vice versa #58112
• feature: We don't have any test automation in place to ensure we aren't adding more opts to our tech debt in the issue [EPIC] Documented options in minion/master config files don't match minion/master config documentation, and vice versa #58112 (such as a recent opt added, fips_mode, via [freeze] fips_mode config option #59833)