1. Proposed title of this feature request
Enhance Argo Rollouts' checking logic for eligibility of promotion

2. What is the nature and description of the request?
During a blue-green deployment, Argo Rollouts will simply recognise the rollout as "initial deploy" whenever the active service lacks an expected hash label selector. However, this logic does not properly tackle the situation that the active service could be unexpectedly modified but the rollout has been successful in advance. I believe we could try to better handle corner cases by utilising the status field (conditions, paused, etc.).

3. Why does the customer need this? (List the business requirements here)
IHAC who was very likely impacted by this corner case and caused an unready preview deployment to be exposed in public, causing service interruption.

4. List any affected packages or components.
OpenShift GitOps - Argo Rollouts