Update module k8s.io/apimachinery to v0.32.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
k8s.io/apimachinery	v0.31.4 -> v0.32.0

---

Release Notes

kubernetes/apimachinery (k8s.io/apimachinery)

v0.32.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

ℹ Artifact update notice

File name: sdk/go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 3 additional dependencies were updated
• The go directive was updated for compatibility reasons

Details:

Package	Change
go	1.22.6 -> 1.23.4
k8s.io/utils	v0.0.0-20240711033017-18e509b52bc8 -> v0.0.0-20241104100929-3ea5e8cea738
sigs.k8s.io/json	v0.0.0-20221116044647-bc3834ca7abd -> v0.0.0-20241010143419-9aa6b5e7a4b3
sigs.k8s.io/structured-merge-diff/v4	v4.4.1 -> v4.4.2

[tityosbot]

Hi @renovate[bot]. Thanks for your PR.

I'm waiting for a giantswarm member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.