Let's write down a policy for go version updates

[justinsb]

I'm not sure if we have written down the policy, but in our LLM-guided future it would be great to write down:

• When we update go minor versions (especially for backports)
• When we update other dependencies (and I suspect here we have a different policy for backports)

[justinsb]

cc @hakman @rifelpet

[rifelpet]

I think a reasonable starting point is to have a kops release's go minor version match that of its k/k dependencies.

[hakman]

We could also upgrade all supported versions, including master, when k/k cherry-picks the new Go version. (unless there is some amazing feature that we want to use very fast).

[hakman]

Seem that's it's pretty hard to not bump Go. After some time, dependencies start pulling the latest k8s version and latest Go comes with it.