chore(linting): add golang-ci lint config (#3899)

* chore(linting): add golang-ci lint config

* more linters

* document more linters

* describe more linters

* describe more linters

* add descriptions

* add descriptions

* config is now valid

* try in action

* add runs on

* dont change out format

* make a change

* make a change

* add timeout

* maybe this way?

* oupsi

* only new issues

* chore: linter settings

* chore: concurRency

* docs(contrib): add linter

* chore: rename github job

* chore: rename github job

* chore(linter): use latest

* chore(linter): version

* chore(action): add working directory

* chore(linting): remove generated files

* build cache

* docs(contrib): recommend golangci-lint as linter in IDE

CONTRIBUTING.md

@@ -115,6 +115,8 @@ With [goreleaser](https://opencollective.com/goreleaser), you build a debuggable
 Then, you test your changes via the console your binary is serving at http://<span because="breaks the link"></span>localhost:8080 and by verifying the database.
 Once you are happy with your changes, you run end-to-end tests and tear everything down.
 
+ZITADEL uses [golangci-lint](https://golangci-lint.run) for code quality checks. Please use [this configuration](.golangci.yaml) when running `golangci-lint`. We recommend to set golangci-lint as linter in your IDE.
+
 The commands in this section are tested against the following software versions:
 
 - [Docker version 20.10.17](https://docs.docker.com/engine/install/)
@@ -122,8 +124,6 @@ The commands in this section are tested against the following software versions:
 - [Go version 1.19](https://go.dev/doc/install)
 - [Delve 1.9.1](https://github.com/go-delve/delve/tree/v1.9.1/Documentation/installation)
 
-<!-- TODO: Describe linting (@adlerhurst) -->
-
 Make some changes to the source code, then run the database locally.
 
 ```bash