Driving toward immutable bundles and adaptable successor identification, we can introduce a release attribute for bundles. This would allow operator authors to re-release a bundle without affecting catalog metadata which would allow for the selection of highest release attribute for a given bundle version.

1. write a [brief](https://docs.google.com/document/d/1tX0fXYuflTpTal6z0TbNkrQ7SAkYIKxQj4cPjlFAh4Q/)
2. write the CSV/FBC RFC
3. [internal] EP review
4. implement CSV (add Release version as an optional field in the CSV api#454)
5. implement FBC (OPRUN-4195,OPRUN-4275,OPRUN-4276: release bundle attribute in version property operator-registry#1792)
6. implement OLMv1 (with a featuregate)
7. implement OLMv0 (ordering only, like here)
8. add documentation (add bundle release version attribute, substitutes template olm-docs#342)