(fix) Helm to Boxcutter migration during OLM upgrade

When upgrading OLM from standard (Helm runtime) to experimental
(Boxcutter runtime), the BoxcutterStorageMigrator creates a
ClusterExtensionRevision from the existing Helm release. However,
the migrated revision was created without status conditions, causing
a race condition where it wasn't recognized as "Installed".

This fix sets an initial Succeeded status on migrated revisions,
ensuring they're immediately recognized and allowing version upgrades
to proceed correctly after OLM upgrades.

Fixes test-upgrade-st2ex-e2e failures.

Author: camilamacedo86

internal/operator-controller/applier/boxcutter.go

@@ -266,6 +266,20 @@ func (m *BoxcutterStorageMigrator) Migrate(ctx context.Context, ext *ocv1.Cluste
 		return fmt.Errorf("getting created revision: %w", err)
 	}
 
+	// Set initial status on the migrated revision to mark it as succeeded.
+	// This ensures the revision is immediately recognized as "Installed" rather than "RollingOut"
+	// when BoxcutterRevisionStatesGetter retrieves revision states.
+	meta.SetStatusCondition(&rev.Status.Conditions, metav1.Condition{
+		Type:               ocv1.ClusterExtensionRevisionTypeSucceeded,
+		Status:             metav1.ConditionTrue,
+		Reason:             "Migrated",
+		Message:            "Migrated from Helm release",
+		ObservedGeneration: rev.GetGeneration(),
+	})
+	if err := m.Client.Status().Update(ctx, rev); err != nil {
+		return fmt.Errorf("updating migrated revision status: %w", err)
+	}
+
 	return nil
 }