Meta Issue for k8s 1.33 bump

[acornett21]

Meta Issue for k8s 1.33 bump

In order to bump Operator SDK to support Kubernetes 1.33 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
• sigs.k8s.io/controller-tools
• operator-framework/operator-manifest-tools updating dependencies to support k8s 1.33 operator-manifest-tools#85

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

• operator-framework/api Update k8s 1 33 api#432

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 updating dependencies to support k8s 1.33 operator-registry#1699
• operator-framework/operator-lib updating dependencies to support k8s 1.33 operator-lib#241

Step 3.2: upgrade kubebuilder

• sigs.k8s.io/kubebuilder/v4 https://github.com/kubernetes-sigs/kubebuilder/releases/tag/v4.6.0

Step 4: upgrade operator-framework plugins

• operator-framework/ansible-operator-plugins updating dependencies to support k8s 1.33 ansible-operator-plugins#151

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

• Bump Ginkgo/v2 and Kubebuilder 1.33 ⚠️ Upgrade from Kubebuilder 4.5.2 to 4.6.0 and add support for k8s 1.33 #6954
• Bump SDK to use k8s 1.33

[acornett21]

@camilamacedo86 FYI ⏫