chore(deps): Bump dependencies

[Ruclo]

What this PR does / why we need it:
Due to go.podman.io/storage v1.61.0 requiring github.com/cyphar/filepath-securejoin v0.5.1,
I decided to fix the version in order to avoid further issues till support for higher version is adapted.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #465

Special notes for your reviewer:

Release note:

NONE

[kubevirt-bot]

[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 dominikholler for approval. For more information see the Code Review Process.

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

Details

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

[sourcery-ai]

Hey - I've found 1 issue, and left some high level feedback:

• The new replace github.com/cyphar/filepath-securejoin => ... v0.5.1 conflicts with the updated indirect requirement to v0.6.1; consider aligning these so that the require section and the enforced version via replace are consistent.
• Most Kubernetes modules were bumped to v0.34.3 but k8s.io/client-go remains at v0.34.2; it’s usually safer to keep these core k8s dependencies on the same patch level unless there’s a specific reason not to.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The new `replace github.com/cyphar/filepath-securejoin => ... v0.5.1` conflicts with the updated indirect requirement to `v0.6.1`; consider aligning these so that the `require` section and the enforced version via `replace` are consistent.
- Most Kubernetes modules were bumped to `v0.34.3` but `k8s.io/client-go` remains at `v0.34.2`; it’s usually safer to keep these core k8s dependencies on the same patch level unless there’s a specific reason not to.

## Individual Comments

### Comment 1
<location> `go.mod:30` </location>
<code_context>
-	k8s.io/apimachinery v0.34.2
+	golang.org/x/crypto v0.47.0
+	golang.org/x/text v0.33.0
+	k8s.io/api v0.34.3
+	k8s.io/apimachinery v0.34.3
 	k8s.io/utils v0.0.0-20251002143259-bc988d571ff4
</code_context>

<issue_to_address>
**issue (bug_risk):** Kubernetes module versions are partially bumped, leaving k8s.io/client-go at 0.34.2, which may cause skew.

Since k8s.io/api and k8s.io/apiextensions-apiserver are now at v0.34.3, it’s safer to align k8s.io/client-go to v0.34.3 as well to avoid version skew and potential subtle incompatibilities. If you need to keep client-go at v0.34.2, please confirm there’s a specific reason or known incompatibility.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

issue (bug_risk): Kubernetes module versions are partially bumped, leaving k8s.io/client-go at 0.34.2, which may cause skew.

Since k8s.io/api and k8s.io/apiextensions-apiserver are now at v0.34.3, it’s safer to align k8s.io/client-go to v0.34.3 as well to avoid version skew and potential subtle incompatibilities. If you need to keep client-go at v0.34.2, please confirm there’s a specific reason or known incompatibility.

[kubevirt-bot]

@Ruclo: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-containerdisks-test	e611976	link	true	/test pull-containerdisks-test

Details

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. I understand the commands that are listed here.

[kubevirt-bot]

PR needs rebase.

Details

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.