Use a more robust CLI color detection

[dani-garcia]

Type of change

- [x] Bug fix
- [ ] New feature development
- [ ] Tech debt (refactoring, code cleanup, dependency upgrades, etc)
- [ ] Build/deploy pipeline (DevOps)
- [ ] Other

Objective

Previously we only did a simple check for NO_COLOR to disable the terminal coloring, and we fell back to isatty otherwise. This would cause it to emit colors in dumb interactive terminals, and at the same time it wouldn't allow for a way to force colors while piping the output.

Switching to the supports-color crate, we don't have to do these checks ourselves while also getting others for free:

• Support for the http://bixense.com/clicolors/ spec, in addition to the https://no-color.org/ spec which we already supported. We can now use CLICOLOR_FORCE=[true|false] to force enable or disable the color regardless of terminal capabilities or interactive status.
• Support for dumb interactive terminals that can't handle colors properly (TERM=dumb).