fix(hcco): align CatalogSource registryPoll interval with OCP defaults

Update HCCO-managed CatalogSource registryPoll interval from 10m to
240m to match standard OCP 4.18+ defaults set by operator-marketplace.

This change:
- Reduces control plane resource consumption from catalog polling
- Decreases etcd churn and storage growth
- Improves scalability for management clusters hosting many HCPs
- Aligns HyperShift behavior with upstream OCP (changed in OCPBUGS-69441)

Trade-off: Catalog update discovery latency increases from 10 minutes
to 4 hours. Users can manually trigger refresh by deleting the
CatalogSource pod if needed.

Signed-off-by: Shital Jadhav <shijadha@redhat.com>
Commit-Message-Assisted-by: Claude (via Claude Code)

Author: shijadha

control-plane-operator/hostedclusterconfigoperator/controllers/resources/olm/catalogs.go

@@ -41,8 +41,8 @@ func reconcileCatalogSource(cs *operatorsv1alpha1.CatalogSource, address string,
 		Priority:  priority,
 		UpdateStrategy: &operatorsv1alpha1.UpdateStrategy{
 			RegistryPoll: &operatorsv1alpha1.RegistryPoll{
-				RawInterval: "10m",
-				Interval:    &metav1.Duration{Duration: 10 * time.Minute},
+				RawInterval: "240m",
+				Interval:    &metav1.Duration{Duration: 240 * time.Minute},
 			},
 		},
 	}