[epic] leverage registry+v1 composite version for bundle ordering

[grokspawn]

With operator-framework/api#454 and operator-framework/operator-registry#1792 merged, we can leverage on-cluster use of the composite bundle version for OLMv1.
For OLMv0, we really do not want to adjust any on-cluster behavior w.r.t. bundle succession, but we can still incorporate the information for bundle version reasoning.

• implement OLMv1 (with a featuregate) #2495
• ClusterExtension versions can be pinned to a release version #2496
• implement OLMv0 (ordering only, like here) operator-lifecycle-manager#3762

[grokspawn]

@rashmigottipati assigned you since you pulled in a couple of these tasks

[rashmigottipati]

@grokspawn sounds good, thanks!

[github-actions]

Issues go stale after 90 days of inactivity. If there is no further activity, the issue will be closed in another 30 days.

[github-actions]

This issue has been closed due to inactivity.