As a maintainer of the CustomResourceDefinition, I want to disable the deprecated API version (v1alpha1) by setting served: false and storage: false, and ensure that all stored Custom Resources are migrated to the new storage version (e.g., v1)
so that the old version can be safely removed in a later release.

Acceptance Criteria:

• The CRD still includes the old version (v1alpha1) but with:

• • served: false

• • storage: false

• Vendor the changes to console-operator