feature: Add support for `NO_COLOR` env var

Latest spec:

• Parse a NO_COLOR env var per instructions at https://no-color.org
• Optionally, also accept --no-color at the CLI.
• Pass this setting to logging configs.
• Pass this setting to click.
• Disable or remove color from rich exception logging, as needed.

Notes:

• This is not to be a feature flag or a Meltano setting, and therefor will not be able to be set using meltano config.
• This should have the equivalent affect as customizing logging.yaml. (Bug fixes in color=false implementation should solve for both methods of setting.)

[aaronsteers]

• From this thread in Slack, we should also try to ensure grayscale codes do not slip through:

https://meltano.slack.com/archives/C01TCRBBJD7/p1662065425046529?thread_ts=1661961091.406679&cid=C01TCRBBJD7

[aaronsteers]

As @pandemicsyn discussed today in a chat:

• Precedence and config methods, the ways of settings are:

  • CLI flag (--no-color)
  • Environment vars (such as NO_COLOR)
  • Default/hidden log config (derived dynamically, will get from the above)
  • Log config (currently highest pri, last applied and overrides above)
    • TODO: take cue from above, if not set in yaml config.

• We still have work to do on no-color compliance:

  • structlog (already applies the the requested color true/false from calling function)
  • Click and our pre-formatted/explicitly-colored print statements that go through Click
    • May be as simple as setting this flag on the parent click context: https://click.palletsprojects.com/en/8.1.x/api/?highlight=color#click.Context.color

We are estimating 4 as size, adding to Engineering Assignments.

cc @tayloramurphy