fix: reduce flaky test by avoiding redundant Cluster updates

The suite test was experiencing flakiness due to intermittent Conflict errors.
Added an early-return check within the RetryOnConflict loop. The logic now
verifies both the label existence/value and the Spec.Paused status before attempting
an update.

Author: gianlucam76

test/fv/fv_suite_test.go

@@ -190,6 +190,13 @@ func verifyCAPICluster() {
 		if currentLabels == nil {
 			currentLabels = make(map[string]string)
 		}
+
+		// Early return only if BOTH conditions are already satisfied
+		val, exists := currentCluster.Labels[key]
+		if exists && val == value && !isTrue(currentCluster.Spec.Paused) {
+			return nil
+		}
+
 		currentLabels[key] = value
 		currentCluster.Labels = currentLabels
 		paused := false
@@ -200,6 +207,10 @@ func verifyCAPICluster() {
 	Expect(err).To(BeNil())
 }
 
+func isTrue(b *bool) bool {
+	return b != nil && *b
+}
+
 func verifySveltosCluster() {
 	clusterList := &libsveltosv1beta1.SveltosClusterList{}
 	listOptions := []client.ListOption{