Is your feature request related to a problem? Please describe.

We have 10 flags to configure logging:
verbose, enable-console-log, encode-json, enable-file-logging, disable-log-color, log-directory, log-file, max-size, max-backups, max-age

Some use enable-* notation, one uses disable-* notation, some prefix the flag with log-* and some don't have a prefix.
Also enable-file-logging use logging while others use log.

We should ensure flags have consistent naming and descriptions.

Describe the solution you'd like

Suggestions:

• verbose - stays the same
• enable-console-log - stays the same, or rename to log-format=console (allowing multiple formats via additional flags)
• enable-file-logging - rename to enable-file-log or to log-format=file (allowing multiple formats via additional flags)
• encode-json - rename to console-log-format or log-format=console-json via feat(logging): Rename encode-json flag to better convey its purpose  #857
• disable-log-color - rename to color with options of on,off,auto. Default auto to detect if environment supports colors, cloud be done via Bug(logging): NO_COLOR env variable is not respected when console logging is enabled #859
• log-directory - stays the same
• log-file - stays the same (maybe rename to log-filename)
• max-size, max-backups, max-age - prefix with log

Describe alternatives you've considered

Move some of the options (like max-size, max-backups, max-age) to config.hcl, but that's tricky since then how do users will be able to control logging before they generate the config

Logging configuration can be set via the config.yml file but should be removed

Additional context

Related to https://github.com/cloudquery/cloudquery/issues?q=is%3Aopen+is%3Aissue+label%3A%22theme%3A+logging%22.

We could do this in a non breaking way via MarkDeprecated and SetNormalizeFunc functions of the Cobra API