✨ Add --no-color option to disable colored output on console

[cp2004]

What does this PR do and why is it necessary?

Add --no-color option to disable colored output on console.

Closes #4396

Also removed the setting of INFO logs to white, instead it will be left as default. If there is a light-colored background (such as white) then it becomes unreadable. Can then just use whatever user has configured for their default and not worry about contrast issues.

> octoprint --help
Usage: octoprint [OPTIONS] COMMAND [ARGS]...

Options:
  -b, --basedir PATH  Specify the basedir to use for configs, uploads,
                      timelapses etc.
  -c, --config PATH   Specify the config file to use.
  --overlay PATH      Specify additional config overlays to use.
  -v, --verbose       Increase logging verbosity.
  --safe              Enable safe mode; disables all third party plugins.
  --no-color          Disable colored console output
  --version           Show the version and exit.
  --help              Show this message and exit.

How was it tested? How can it be tested by the reviewer?

Manually by starting with and without the flag.

[zaitcev]

Looks okay to me, although weirdly different from existing code in a tiny detail.

[zaitcev]

Why are we changing the style of boolean? The safe mode uses None-not-None, and we have Python bool for no-color. Seems perhaps unnecessarily inconsistent, if I may bikeshed a little.

[foosel]

safe_mode is a special case, as it doesn't set a boolean value but rather a source of the safe mode activation. If it is anything but None, OctoPrint will run in safe mode, but it will log the reason for that based on the value of this flag.

However, the explicit cast to bool should indeed not be needed here, as this should already be a boolean thanks to being marked with is_flag=True in the click def.