Set state_output_profile as option and update docs

[ScriptAutomate]

What does this PR do?

• Documents state_output_profile as an option in master and minion configs
• Adds state_output_profile as an option to salt/config/__init__.py, validating as a bool
• Adds state_output_profile as having default value of True in minion and master configs
• Updates salt/output/highstate.py to no longer hard-code default value for state_output_profile

What issues does this PR fix or reference?

Ongoing work related to: #58112

It looks like state_output_profile was meant to be an option, but was instead hard-coded into salt/output/highstate.py when the value and option should have been documented for minion/master configurations.

• Fixes changes done by old PR: Default state_output_profile to True everywhere, closes #35166 #35271
• Fixes original issue: state_output_profile defaults are confusing #35166

Previous Behavior

Undocumented option.

New Behavior

Documented option.

Merge requirements satisfied?

[NOTICE] Bug fixes or features added to Salt require tests.

• Docs
• Changelog - https://docs.saltstack.com/en/master/topics/development/changelog.html
• Tests written/updated

Commits signed with GPG?

Yes

[ScriptAutomate]

Of note: I also opened #59166 after noticing that we may need to extend the salt/output/highstate.py docstring documentation to include state_output_diff and state_output_profile information. The issue also notes that show_output documentation in the highstate.py docstring docs differs from the master/minion config definition of what valid values are acceptable.

[waynew]

🚀 Looks great!

[waynew]

Looks like in JsonNestedTestCase in the setup_loader_modules function you'll need to add "state_output_profile": True, as well

[ScriptAutomate]

@waynew said: Looks like in JsonNestedTestCase in the setup_loader_modules function you'll need to add "state_output_profile": True, as well

Thanks!

I've now changed here:

• 2c5ee76

pre-commit applied everything else here:

• 279c9a4

[waynew]

🚀