Fine-tune the Revive linter

[MichaelSnowden]

What changed?
I turned on every linter for Revive except a few handpicked ones that I thought weren't useful.

Why?
We don't want to enable some useless linters like exported, but having linters like cyclomatic for new code seem really useful.

How did you test it?
I ran it locally. I also inspected the actual errors generated using this JQ query to see if they made sense:

golangci-lint run  --verbose --out-format=json --max-issues-per-linter=0 --max-same-issues 1 \
  | jq '.Issues | map((.Text| split(": ") | {"Rule": .[0], "Value": .[1]}) + {"Key": "./\(.Pos.Filename):\(.Pos.Line)"}) | group_by(.Rule) | map({"Rule": .[0].Rule, Violations: ([.[]] | from_entries )}) | sort_by(.Violations | length)'

Potential risks
It's just a linter

Is hotfix candidate?
No

[alexshtin]

Is it possible not to include enabled rules? If new rules are added later I would like them to be enabled by default and only some of them explicitly disabled.

[MichaelSnowden]

Yes it is. Fixed

[alexshtin]

Please fix PR description also :-)