As a user I want to have a consistent experience with run-time OSSM/GWAPI, and know which version of OSSM is aligned with which version of OCP.

• Investigate the pros and cons of pinning to a subscription release version of OSSM.
• Determine whether we can pin to z-streams of OSSM.
• Work with OSSM to get feedback on the approach, because we don't want to unnecessarily slow down OSSM upgrades.

We currently configure automatic subscription upgrades: https://github.com/openshift/cluster-ingress-operator/blob/master/pkg/operator/controller/gatewayclass/subscription.go#L59

We can change that to installPlanApproval: Manual as outlined in https://olm.operatorframework.io/docs/concepts/crds/subscription/#manually-approving-upgrades-via-subscriptions.

Pros: changes to OSSM operators that we have not tested will not be released automatically Cons: later updates might be more difficult.

Brief slack discussion: https://redhat-internal.slack.com/archives/C03S6Q5KB8W/p1687812972469569