Verify that Gatekeeper CRDs are not affected by K8s CABundle validation on CRD

[JaydipGabani]

Let's make sure that Gatekeeper CRDs are not affected by kubernetes/kubernetes#124061, which is included in k8s 1.31.

The change makes sure that CustomResourceDefinition objects created with non-empty caBundle fields which are invalid or do not contain any certificates will not appear in discovery or serve endpoints until a valid caBundle is provided. Updates to CustomResourceDefinition are no longer allowed to transition a valid caBundle field to an invalid caBundle field, because this breaks serving of the existing CustomResourceDefinition.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.