fix: update e2e tests to expect Progressing=False on successful rollout

Update ClusterExtension e2e assertions to match the corrected
Progressing condition semantics. ClusterObjectSet assertions are
unchanged as they use a separate controller.

Signed-off-by: Venkatesh Durgam <vdurgam@redhat.com>
Co-authored-by: Cursor <cursoragent@cursor.com>

Author: vdurgam10

test/e2e/features/install.feature

@@ -676,5 +676,5 @@ Feature: Install ClusterExtension
       """
     When ServiceAccount "olm-sa" with needed permissions is available in test namespace
     Then ClusterExtension is available
-    And ClusterExtension reports Progressing as True with Reason Succeeded
+    And ClusterExtension reports Progressing as False with Reason Succeeded
     And ClusterExtension reports Installed as True

test/e2e/features/recover.feature

@@ -54,7 +54,7 @@ Feature: Recover cluster extension from errors that might occur during its lifet
     And ClusterExtension reports Progressing as True with Reason Retrying
     When ServiceAccount "olm-sa" with needed permissions is available in test namespace
     Then ClusterExtension is available
-    And ClusterExtension reports Progressing as True with Reason Succeeded
+    And ClusterExtension reports Progressing as False with Reason Succeeded
 
   Scenario: Install ClusterExtension after conflicting resource is removed
     Given ServiceAccount "olm-sa" with needed permissions is available in test namespace
@@ -114,7 +114,7 @@ Feature: Recover cluster extension from errors that might occur during its lifet
     And ClusterExtension reports Installed as False
     When resource "deployment/test-operator-${SCENARIO_ID}" is removed
     Then ClusterExtension is available
-    And ClusterExtension reports Progressing as True with Reason Succeeded
+    And ClusterExtension reports Progressing as False with Reason Succeeded
     And ClusterExtension reports Installed as True
 
   @PreflightPermissions
@@ -149,7 +149,7 @@ Feature: Recover cluster extension from errors that might occur during its lifet
       """
     When ServiceAccount "olm-sa" with needed permissions is available in test namespace
     Then ClusterExtension is available
-    And ClusterExtension reports Progressing as True with Reason Succeeded
+    And ClusterExtension reports Progressing as False with Reason Succeeded
     And ClusterExtension reports Installed as True
 
   # CATALOG DELETION RESILIENCE SCENARIOS
@@ -250,6 +250,6 @@ Feature: Recover cluster extension from errors that might occur during its lifet
                 "olm.operatorframework.io/metadata.name": ${CATALOG:test}
       """
     And ClusterExtension latest generation has been reconciled
-    And ClusterExtension reports Progressing as True with Reason Succeeded
+    And ClusterExtension reports Progressing as False with Reason Succeeded
     Then ClusterExtension is available
     And ClusterExtension reports Installed as True

test/e2e/steps/steps.go

@@ -584,7 +584,7 @@ func ClusterExtensionReconciledLatestGeneration(ctx context.Context) error {
 	return nil
 }
 
-// ClusterExtensionIsRolledOut waits for the ClusterExtension's Progressing condition to be True with reason Succeeded,
+// ClusterExtensionIsRolledOut waits for the ClusterExtension's Progressing condition to be False with reason Succeeded,
 // then gathers its constituent resources into the scenario context. Polls with timeout.
 func ClusterExtensionIsRolledOut(ctx context.Context) error {
 	sc := scenarioCtx(ctx)
@@ -599,7 +599,7 @@ func ClusterExtensionIsRolledOut(ctx context.Context) error {
 			return false
 		}
 
-		return condition["status"] == "True" && condition["reason"] == "Succeeded" && condition["type"] == "Progressing"
+		return condition["status"] == "False" && condition["reason"] == "Succeeded" && condition["type"] == "Progressing"
 	}, timeout, tick)
 
 	if rec := RecorderFromContext(ctx); rec != nil {