Add linter to CI checks #237
Description
There are bugs and technical debt which could be detected by running a linter (static analysis) on the code, as shown in #234
We should consider adding a linter to the CI so that this can be detected on per-PR basis before it's merged.
It's likely that different linters have different features, so we should find out what they offer and whether at all it makes sense to combine them.
TODO: Look at these:
- https://staticcheck.io/
- https://pkg.go.dev/golang.org/x/lint/golint?tab=overview
- https://golang.org/cmd/vet/
Ideally though I would like to avoid reporting checks which have potential for false negatives and avoid adding comments into the code which suppress these false linter warnings. I have seen this in a repository which uses https://github.com/golangci/golangci-lint