fix(deps): update kubernetes go patches to v0.34.2

[octo-sts]

This PR contains the following updates:

Package	Change	Age	Confidence
k8s.io/api	v0.34.1 -> v0.34.2
k8s.io/apiextensions-apiserver	v0.34.1 -> v0.34.2
k8s.io/apimachinery	v0.34.1 -> v0.34.2
k8s.io/apiserver	v0.34.1 -> v0.34.2
k8s.io/cli-runtime	v0.34.1 -> v0.34.2
k8s.io/client-go	v0.34.1 -> v0.34.2
k8s.io/component-base	v0.34.1 -> v0.34.2

---

Release Notes

kubernetes/api (k8s.io/api)

v0.34.2

Compare Source

kubernetes/apiextensions-apiserver (k8s.io/apiextensions-apiserver)

v0.34.2

Compare Source

kubernetes/apimachinery (k8s.io/apimachinery)

v0.34.2

Compare Source

kubernetes/apiserver (k8s.io/apiserver)

v0.34.2

Compare Source

kubernetes/cli-runtime (k8s.io/cli-runtime)

v0.34.2

Compare Source

kubernetes/client-go (k8s.io/client-go)

v0.34.2

Compare Source

kubernetes/component-base (k8s.io/component-base)

v0.34.2

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 becomes conflicted, or you tick the rebase/retry checkbox.

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

---

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

---

This PR has been generated by Renovate Bot.

[cert-manager-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign munnerz for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[cert-manager-prow]

Hi @octo-sts[bot]. Thanks for your PR.

I'm waiting for a cert-manager 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-sigs/prow repository.