Description of problem

Under certain conditions, the OLM operator will create multiple install plans for the same cluster service version. If this happens with the ingress operator's OSSM subscription, the ingress operator will only approve the first matching install plan it finds, and if that is not the most recent install plan, the OLM operator may not install OSSM.

Version-Release number of selected component (if applicable)

4.19 with the TechPreviewNoUpgrade feature set.

How reproducible

50% of the time.

Steps to Reproduce

1. Launch an OCP 4.19 cluster with the TechPreviewNoUpgrade featureset.
2. Create a gatewayclass to cause cluster-ingress-operator to install OSSM:

oc create -f -<<'EOF'                                                 
apiVersion: gateway.networking.k8s.io/v1beta1    
kind: GatewayClass           
metadata:    
  name: openshift-default                                   
spec:              
  controllerName: openshift.io/gateway-controller/v1
EOF

3. Check the subscription:

oc -n openshift-operators get subscriptions/servicemeshoperator3 -o yaml

Actual results

The subscription fails to install. TODO: The diagnostic for this failure mode needs to be described!

Expected results

The subscription installs successfully.