Add golang linter

[scaps1]

Description

Add golangci linter

Why do we need it, and what problem does it solve?

This linter needs for scanning Go code files

Why do we need it in the patch release (if we do)?

Not necessarily"

Checklist

• The code is covered by unit tests.
• e2e tests passed.
• Documentation updated according to the changes.
• Changes were tested in the Kubernetes cluster manually.

Changelog entries

 type: fix | feature | chore
 summary: <ONE-LINE of what effectively changes for a user>
 impact: <what to expect for users, possibly MULTI-LINE>, required if impact_level is high ↓
 impact_level: default | high | low