Meta Issue for k8s 1.30 bump

[Neo2308]

Meta Issue for k8s 1.30 bump

In order to bump Operator SDK to support Kubernetes 1.30 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 (https://github.com/kubernetes-sigs/controller-runtime/releases/tag/v0.18.0)
• sigs.k8s.io/controller-tools (https://github.com/kubernetes-sigs/controller-tools/releases/tag/v0.15.0)
• operator-framework/operator-manifest-tools (Updating k8s to 1.30 & go to 1.22 operator-manifest-tools#57)

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

• operator-framework/api (K8s 1.30 version update and go 1.22 api#322)

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 k8s libraries to v0.30.0 operator-registry#1297)
• operator-framework/operator-lib (bump go to 1.22, k8s deps to 0.30.0 operator-lib#176)

Step 3.2: upgrade kubebuilder

• sigs.k8s.io/kubebuilder/v3

Step 4: upgrade operator-framework plugins

• operator-framework/ansible-operator-plugins
• operator-framework/helm-operator-plugins (bump go 1.22 and k8s 1.30 helm-operator-plugins#337)
• operator-framework/java-operator-plugins

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

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

[Neo2308]

Copied from #6651
Removed "sigs.k8s.io/kubebuilder-declarative-pattern" based on #6651 (comment)

[Neo2308]

K8s 1.30 support for kubebuilder would be coming post the major bump in kubebuilder version.
Ref: kubernetes-sigs/kubebuilder#3622