With https://github.com/operator-framework/api/pull/454 and https://github.com/operator-framework/operator-registry/pull/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)
• [ ] ClusterExtension versions can be pinned to a release version
• [ ] implement OLMv0 (ordering only, like [here](https://github.com/operator-framework/operator-lifecycle-manager/blob/d55d4899c17db9caeb90aac2ec86d5c82651593a/pkg/package-server/provider/registry.go#L331))