[release/v1.7] Update Go to 1.21.5 and machine-controller to v1.57.4

[xmudrii]

What this PR does / why we need it:

Update Go to 1.21.5 and machine-controller to v1.57.4 on the release/v1.7 branch (cherry-pick of #2988).

What type of PR is this?

/kind feature

Does this PR introduce a user-facing change? Then add your Release Note here:

- KubeOne is now built with Go 1.21.5
- Update machine-controller to v1.57.4

Documentation:

NONE

/assign @kron4eg

[xmudrii]

/test pull-kubeone-e2e-aws-default-install-containerd-v1.25.11

[embik]

/retest

[embik]

We bumped sonobuoy in https://github.com/kubermatic/infra/pull/2501 from 0.56.16 to 0.57.1, I'm pretty sure that's the reason the jobs are starting to fail.

[embik]

I think sonobuoy wait is just broken in 0.57. I see vmware-tanzu/sonobuoy#1909 as a candidate for breaking it, but haven't validated that yet. But the same thing happens on a KKP user cluster:

$ sonobuoy run --mode=conformance-lite --dns-pod-labels "app.kubernetes.io/name=kube-dns,app=coredns" && sonobuoy wait
INFO[0000] create request issued                         name=sonobuoy namespace= resource=namespaces
INFO[0000] create request issued                         name=sonobuoy-serviceaccount namespace=sonobuoy resource=serviceaccounts
INFO[0000] create request issued                         name=sonobuoy-serviceaccount-sonobuoy namespace= resource=clusterrolebindings
INFO[0000] create request issued                         name=sonobuoy-serviceaccount-sonobuoy namespace= resource=clusterroles
INFO[0000] create request issued                         name=sonobuoy-config-cm namespace=sonobuoy resource=configmaps
INFO[0000] create request issued                         name=sonobuoy-plugins-cm namespace=sonobuoy resource=configmaps
INFO[0000] create request issued                         name=sonobuoy namespace=sonobuoy resource=pods
INFO[0000] create request issued                         name=sonobuoy-aggregator namespace=sonobuoy resource=services
ERRO[0000] error attempting to run sonobuoy: waiting for run to finish: context deadline exceeded

sonobuoy wait just fails instantly:

$ time sonobuoy wait
ERRO[0000] error attempting to run sonobuoy: waiting for run to finish: context deadline exceeded
sonobuoy wait  0.03s user 0.01s system 14% cpu 0.295 total

[embik]

Okay, it seems this is intended behaviour of sonobuoy wait? You need to pass sonobuoy wait --wait to actually get that, otherwise the default value of 0 for --wait means that there will be no wait.

[kron4eg]

/lgtm
/approve

[kubermatic-bot]

LGTM label has been added.

Git tree hash: 26f3831bad21e20c6d1ae58b70cf34b62347c68c

[kubermatic-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kron4eg

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [kron4eg]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kpython]

When installing kubeone_1.7.2_darwin_arm64.zip, I still see "goVersion": "go1.21.3"
Shouldn't be go1.21.5 ?