dev: enhance help linters output on fast and auto-fix capabilities

[alexandear]

The PR changes the output for the golangci-lint linters help command.
I think outputting [fast: false, auto-fix: false] is redundant, and help prints nothing if the linter is slow and does not have auto-fix. If a linter is fast, the command prints green [fast]. If a linter can auto fix, the command prints green [auto-fix]. If a linter is fast and has auto fix - [fast, auto-fix] in green.

Before

After

[ccoVeille]

I like the colors.

But there is something strange with the non-fast one. I find uneasy to visually spot the ones that are not available in fast mode.

[ccoVeille]

Maybe [non-fast] in orange?

UI is never fun.

This is a random feedback, feel free to ignore or wait for ldez feedback

[ldez]

This will make it more complex to filter linter with grep.
I prefer to be able to use grep over having colors.

Also, IMO, having different colors for "fast"/"slow" is not right because it will imply a negative impression of "slow" linters.

[alexandear]

This will make it more complex to filter linter with grep.

Maybe we can introduce flags for this use case:

• golangci-lint help linters --fast
• golangci-lint help linters --auto-fix

[ldez]

This will not work because the help contains more than linters, so grep is still the best approach.

It will also create an unnecessary complexity just for a help command.

[ldez]

After more thinking, I have a better idea to solve the grep problem, I will do a PR on this topic.
With my approach, the missing boolean will not be a problem.

If my PR works, we will merge the 2 PRs.

[ldez]

I opened #5209

[ldez]

new render:

(note: I don't have the same color render as you)

[ldez]

LGTM