[DOCS] Review highstate outputter docs and state_output docs option

[ScriptAutomate]

Description

The highstate outputter salt/output/highstate.py provides conflicting information about state_output when compared to the minion and master config option documentation.

Suggested Fix

• If extra potential values exist, such as filter, then the minion/master config documentation needs to be updated.
• Evaluate whether state_output_diff and state_output_profile need to be included in the docstring documentation found in salt/output/highstate.py

Type of documentation

• Salt documentation

Location or format of documentation

salt/salt/output/highstate.py

Lines 17 to 52 in 318502a

	state_output:
	The highstate outputter has six output modes,
	``full``, ``terse``, ``mixed``, ``changes`` and ``filter``
	* The default is set to ``full``, which will display many lines of detailed
	information for each executed chunk.
	* If ``terse`` is used, then the output is greatly simplified and shown in
	only one line.
	* If ``mixed`` is used, then terse output will be used unless a state
	failed, in which case full output will be used.
	* If ``changes`` is used, then terse output will be used if there was no
	error and no changes, otherwise full output will be used.
	* If ``filter`` is used, then either or both of two different filters can be
	used: ``exclude`` or ``terse``.
	* for ``exclude``, state.highstate expects a list of states to be excluded (or ``None``)
	followed by ``True`` for terse output or ``False`` for regular output.
	Because of parsing nuances, if only one of these is used, it must still
	contain a comma. For instance: `exclude=True,`.
	* for ``terse``, state.highstate expects simply ``True`` or ``False``.
	These can be set as such from the command line, or in the Salt config as
	`state_output_exclude` or `state_output_terse`, respectively.
	The output modes have one modifier:
	``full_id``, ``terse_id``, ``mixed_id``, ``changes_id`` and ``filter_id``
	If ``_id`` is used, then the corresponding form will be used, but the value for ``name``
	will be drawn from the state ID. This is useful for cases where the name
	value might be very long and hard to read.

vs.

salt/conf/master

Lines 625 to 631 in 318502a

	# The state_output setting controls which results will be output full multi line
	# full, terse - each state will be full/terse
	# mixed - only states with errors will be full
	# changes - states with changes and errors will be full
	# full_id, mixed_id, changes_id and terse_id are also allowed;
	# when set, the state ID will be used as name in the output
	#state_output: full

salt/conf/minion

Lines 695 to 701 in 318502a

	# The state_output setting controls which results will be output full multi line
	# full, terse - each state will be full/terse
	# mixed - only states with errors will be full
	# changes - states with changes and errors will be full
	# full_id, mixed_id, changes_id and terse_id are also allowed;
	# when set, the state ID will be used as name in the output
	#state_output: full

• https://github.com/saltstack/salt/blob/master/doc/ref/configuration/minion.rst#state_output
• https://github.com/saltstack/salt/blob/master/doc/ref/configuration/master.rst#state_output

Additional context

Potentially related or of interest: #51090