Issue 17655699: console ClusterOperator should not blip Available=False with the reason=Deployment_InsufficientReplicas
Description: Seeing it in 4.21 non-upgrade jobs.
 
 [periodic-ci-openshift-hypershift-release-4.18-periodics-e2e-aws-ovn-conformance-serial|https://sippy-auth.dptools.openshift.org/sippy-ng/component_readiness/test_details?Architecture=amd64&FeatureSet=default&Installer=hypershift&LayeredProduct=none&Network=ovn&Platform=aws&Suite=serial&Topology=external&Upgrade=none&baseEndTime=2025-10-21T23%3A59%3A59Z&baseRelease=4.20&baseStartTime=2025-09-21T00%3A00%3A00Z&capability=Operator&columnGroupBy=Network%2CPlatform%2CTopology&component=kube-storage-version-migrator&confidence=95&dbGroupBy=Architecture%2CFeatureSet%2CInstaller%2CLayeredProduct%2CNetwork%2CPlatform%2CSuite%2CTopology%2CUpgrade&environment=Architecture%3Aamd64+FeatureSet%3Adefault+Installer%3Ahypershift+LayeredProduct%3Anone+Network%3Aovn+Platform%3Aaws+Suite%3Aserial+Topology%3Aexternal+Upgrade%3Anone&flakeAsFailure=false&ignoreDisruption=true&ignoreMissing=false&includeMultiReleaseAnalysis=true&includeVariant=Architecture%3Aamd64&includeVariant=Architecture%3Aarm64&includeVariant=Architecture%3Amulti&includeVariant=CGroupMode%3Av2&includeVariant=ContainerRuntime%3Acrun&includeVariant=ContainerRuntime%3Arunc&includeVariant=FeatureSet%3Adefault&includeVariant=FeatureSet%3Atechpreview&includeVariant=Installer%3Ahypershift&includeVariant=Installer%3Aipi&includeVariant=Installer%3Aupi&includeVariant=JobTier%3Ablocking&includeVariant=JobTier%3Ainforming&includeVariant=JobTier%3Astandard&includeVariant=LayeredProduct%3Anone&includeVariant=LayeredProduct%3Avirt&includeVariant=Network%3Aovn&includeVariant=Owner%3Aeng&includeVariant=Owner%3Aservice-delivery&includeVariant=Platform%3Aaws&includeVariant=Platform%3Aazure&includeVariant=Platform%3Agcp&includeVariant=Platform%3Ametal&includeVariant=Platform%3Arosa&includeVariant=Platform%3Avsphere&includeVariant=Topology%3Aexternal&includeVariant=Topology%3Aha&includeVariant=Topology%3Amicroshift&minFail=3&passRateAllTests=0&passRateNewTests=95&pity=5&sampleEndTime=2025-12-09T12%3A00%3A00Z&sampleRelease=4.21&sampleStartTime=2025-12-02T00%3A00%3A00Z&testBasisRelease=4.18&testId=openshift-tests%3A33465aa3f116f78b5ce13a25e64e13cc]
 
 [Example1|https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-hypershift-release-4.21-periodics-e2e-aws-ovn-conformance-serial/1997108951224684544]
 
 [Example2|https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-hypershift-release-4.21-periodics-e2e-aws-ovn-conformance-serial/1996746545671704576]
 
 [Example3|https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-hypershift-release-4.21-periodics-e2e-aws-ovn-conformance-serial/1996384152387063808]
 
  
 {noformat}
 : [Monitor:legacy-cvo-invariants][bz-Management Console] clusteroperator/console should not change condition/Available expand_less2h11m40s{  2 unexpected clusteroperator state transitions during e2e test run.  These did not match any known exceptions, so they cause this test-case to fail:
 
 Dec 06 01:49:25.064 E clusteroperator/console condition/Available reason/Deployment_InsufficientReplicas status/False DeploymentAvailable: 0 replicas available for console deployment
 Dec 06 01:49:25.064 - 10s   E clusteroperator/console condition/Available reason/Deployment_InsufficientReplicas status/False DeploymentAvailable: 0 replicas available for console deployment
 
 1 unwelcome but acceptable clusteroperator state transitions during e2e test run.  These should not happen, but because they are tied to exceptions, the fact that they did happen is not sufficient to cause this test-case to fail:
 
 Dec 06 01:49:35.881 W clusteroperator/console condition/Available reason/AsExpected status/True All is well (exception: Available=True is the happy case)
 } {noformat}
Status: New