Add Makefile target to upgrade OLMv0 install to OLMv1 install

[coderabbitai]

Overview

Add a make target (e.g., make upgrade-v0-to-olmv1) that automates upgrading an existing OADP operator installation managed by OLMv0 (Subscription/OperatorGroup) to be managed by OLMv1 (ClusterExtension).

Background

PR #2160 introduces OLMv1 lifecycle Makefile targets (test-olmv1, test-olmv1-cleanup) for fresh OLMv1 installs. However, there is no automation for the migration/upgrade scenario where an operator is already installed via OLMv0 and needs to be transitioned to OLMv1 management.

Goals

• Add a parameterized Makefile target (e.g., make upgrade-v0-to-olmv1) that:
  1. Detects/removes the existing OLMv0 Subscription and OperatorGroup for OADP.
  2. Creates the necessary ServiceAccount and RBAC (ClusterRoleBinding) for the OLMv1 installer.
  3. Creates a ClusterExtension pointing to the desired package/channel/version.
  4. Waits for the ClusterExtension to reach Installed=True.
• Reuse existing OLMV1_* Makefile variables (package, namespace, channel, version, catalog, catalog-image, service-account) introduced in PR OADP-7235: OLMv1 lifecycle tests + OLMv0→OLMv1 migration target #2160 for consistency.
• Handle inline.watchNamespace (OLMv1) vs. watchNamespace env var / OperatorGroup scope (OLMv0) differences.

References

• PR OADP-7235: OLMv1 lifecycle tests + OLMv0→OLMv1 migration target #2160: OADP-7235: OLMv1 lifecycle tests + OLMv0→OLMv1 migration target #2160
• Related issue Test OLMv0 to OLMv1 upgrade path/migration #2193 (test coverage for OLMv0→OLMv1 migration): Test OLMv0 to OLMv1 upgrade path/migration #2193
• OLMv0 install mode in CSV:

  oadp-operator/config/manifests/bases/oadp-operator.clusterserviceversion.yaml

  Lines 467 to 475 in 7e53a85

  	installModes:
  	- supported: true
  	type: OwnNamespace
  	- supported: false
  	type: SingleNamespace
  	- supported: false
  	type: MultiNamespace
  	- supported: false
  	type: AllNamespaces

• OLMv0 watchNamespace config:

  oadp-operator/config/manager/manager.yaml

  Lines 63 to 66 in 7e53a85

  	- name: WATCH_NAMESPACE
  	valueFrom:
  	fieldRef:
  	fieldPath: metadata.namespace

Requested by @kaovilai on PR #2160 comment: #2160

[openshift-ci]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale