[epic] Add registry+v1 bundle release attribute

[grokspawn]

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
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. add documentation (add bundle release version attribute, substitutes template olm-docs#342)

on-cluster operations split to #2479

[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.