Enable revive linter

[yurishkuro]

Which problem is this PR solving?

• revive is a pretty comprehensive linter that catches many issues
• incidentally, I wanted to have a linter for the change in chore: use errors.New to replace fmt.Errorf with no parameters will much better #5377, but the errorf rule in revive is only catching errors.New(fmt.Sprintf()), not fmt.Errorf(just_string) scenarios.

Description of the changes

• add revive to the main list of linters
• disable some of its rules which are currently breaking for future clean-up
• clean-up a few places what had low number of breaks

How was this change tested?

• make lint

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.18%. Comparing base (ca50f53) to head (be663cc).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5505      +/-   ##
==========================================
- Coverage   96.19%   96.18%   -0.02%     
==========================================
  Files         327      327              
  Lines       16012    16012              
==========================================
- Hits        15403    15401       -2     
- Misses        435      436       +1     
- Partials      174      175       +1     

Flag	Coverage Δ
badger_v1	8.05% <ø> (ø)
badger_v2	1.93% <0.00%> (ø)
cassandra-3.x-v1	16.43% <ø> (ø)
cassandra-3.x-v2	1.85% <0.00%> (ø)
cassandra-4.x-v1	16.43% <ø> (ø)
cassandra-4.x-v2	1.85% <0.00%> (ø)
elasticsearch-7-v1	18.88% <ø> (-0.02%)	⬇️
elasticsearch-8-v1	19.08% <ø> (ø)
elasticsearch-8-v2	19.07% <ø> (-0.02%)	⬇️
grpc_v1	9.47% <ø> (-0.02%)	⬇️
grpc_v2	7.53% <0.00%> (ø)
kafka	9.78% <ø> (ø)
opensearch-1-v1	18.94% <ø> (ø)
opensearch-2-v1	18.94% <ø> (+0.01%)	⬆️
opensearch-2-v2	18.94% <ø> (+0.01%)	⬆️
unittests	93.87% <100.00%> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.