Meta Issue for k8s 1.34 bump #7020

Meta Issue for k8s 1.34 bump

In order to bump Operator SDK to support Kubernetes 1.34 there are a few dependencies we rely on making the bump first.
This issue is meant to help track all dependencies and the status of their bumps.

Order of dependency bumps

Step 1: upgrade controller-runtime, controller-tools, helm, and operator-framework/operator-manifest-tools(can be done in parallel)

• sigs.k8s.io/controller-runtime 🌱Update k8s.io dependencies to v0.34.0 kubernetes-sigs/controller-runtime#3300
• sigs.k8s.io/controller-tools ⚠️ Bump to k8s.io/* v0.34 kubernetes-sigs/controller-tools#1266
• operator-framework/operator-manifest-tools chore(deps): bump k8s.io/apimachinery from 0.33.4 to 0.34.1 operator-manifest-tools#96

Step 2: upgrade operator-framework/api (can be done immediately after controller-runtime & controller-tools)

• operator-framework/api Bump the k8s-dependencies group with 5 updates api#447

Step 3.1: upgrade operator-framework/operator-registry and operator-framework/operator-lib (can be done immediately after operator-framework/api)

• operator-framework/operator-registry Bump the k8s-dependencies group across 1 directory with 6 updates operator-registry#1772
• operator-framework/operator-lib 🌱 Bump github.com/operator-framework/api from 0.33.0 to 0.34.0 operator-lib#254

Step 3.2: upgrade kubebuilder

• sigs.k8s.io/kubebuilder/v4 🌱 Add k8s 1.34 version set for tooling - prow tests kubernetes-sigs/kubebuilder#5146

Step 4: upgrade operator-framework plugins

• operator-framework/ansible-operator-plugins

Step 5: upgrade operator-framework/operator-sdk dependencies

• Bump Ginkgo/v2 and Kubebuilder 1.34
• Bump SDK to use k8s 1.34