Meta Issue for K8S 1.27

[oceanc80]

Meta Issue for k8s 1.27 bump

In order to bump Operator SDK to support Kubernetes 1.27 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

Step 2: upgrade operator-framework/api and sigs.k8s.io/kubebuilder-declarative-pattern (can be done immediately after controller-runtime)

• operator-framework/api
• sigs.k8s.io/kubebuilder-declarative-pattern

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 operator-framework/api dependency which has k8s 1.27 changes operator-registry#1120
• operator-framework/operator-lib

Step 3.2: upgrade kubebuilder (blocked until kubebuilder-declarative-pattern is bumped)

• sigs.k8s.io/kubebuilder/v3

Step 4: upgrade operator-framework/helm-operator-plugins and operator-framework/java-operator-plugins

• operator-framework/helm-operator-plugins Bump controller-runtime and k8s.io deps helm-operator-plugins#216
• operator-framework/java-operator-plugins Bump k8s packages to v0.27.2 java-operator-plugins#119

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

• Bump Ginkgo/v2 and Kubebuilder 1.27
• Bump SDK to use k8s 1.27
• Bump envtest to 1.27