Improve argparse documentation about controlling color

[savannahostrowski]

Related to #139946 (comment), we should improve argparse documentation to clarify the order of precedence of controlling color by expanding this section a bit https://docs.python.org/3/library/argparse.html#color.

Some notes to get started:

• Environment variables take precedence over color=True, but color=False takes precedence.
• Users can control global color settings via NO_COLOR or FORCE_COLOR etc.

Linked PRs

• gh-140693: Improve argparse documentation about controlling color #140737
• [3.14] gh-140693: Improve argparse documentation about controlling color (GH-140737) #140932

[XChaitanyaX]

Working on this..

[XChaitanyaX]

Really, what we want to spell out is that env vars take precedence over anything set in the parser.

Why does FORCE_COLOR = "1" and color=False does not give colored output??

[savannahostrowski]

Sorry, that's a typo. Below that, I have a note that color=False actually takes precedence.

Environment variables take precedence over color=True, but color=False takes precedence.

It's worth tracing through the code, though, as you update the docs. I think there may be more context worth adding as well.

[hugovk]

Note https://docs.python.org/3/using/cmdline.html#using-on-controlling-color details the precedence of the env vars, so we can refer to that.

And in originally implementing, I also aimed to follow https://no-color.org/ about color=, see FAQ 2: "How should configuration files and command-line arguments be processed in the presence of NO_COLOR?"