enable linter, update to g/g 1.30.2, update to go 1.18

[majst01]

replaces #214

[Gerrit91]

With just linter fixes we can merge immediately, don't think the Gardener update is necessary right now?
The linter action introduces double-linting, effectively increasing the build time. Maybe we can try providing an own config file in order not to slow down the build even further: https://github.com/gardener/gardener/blob/v1.27.5/hack/check.sh#L23

[majst01]

With just linter fixes we can merge immediately, don't think the Gardener update is necessary right now? The linter action introduces double-linting, effectively increasing the build time. Maybe we can try providing an own config file in order not to slow down the build even further: https://github.com/gardener/gardener/blob/v1.27.5/hack/check.sh#L23

Build time increased ~1m according to https://github.com/metal-stack/gardener-extension-provider-metal/actions

[majst01]

I would merge with the g/g update and use this for the next round of g/g update in our environment

[Gerrit91]

I don't think we need the Gardener dependency update because the other extension providers from them also only have builds for 1.27 or 1.29.

[Gerrit91]

Also why 1.28.0 and not the latest patch version of this release?

[majst01]

What about going to 1.30 straight ?

[Gerrit91]

Can you rebase and maybe even rename the branch? We can soon proceed with Gardener 1.30 and this PR would be great for that.

[majst01]

Can you rebase and maybe even rename the branch? We can soon proceed with Gardener 1.30 and this PR would be great for that.

Branch rename would make this PR invalid, keep it

[mwennrich]

not so important, but mcm-deps could also be bumped: https://github.com/metal-stack/releases/blob/v0.10.2/release.yaml#L54-L61

[Gerrit91]

Will do this in the Gardener 1.31 PR. :)