Once the operator and bundle image have been built (and before handover to QE), we need to verify that the bundle image metadata is correct.

1. skipRange must be valid and determine if still required (not needed in all bundles)
2. if a skipRange is present then a replace must be present to (in order to preserve the release chains in the channel)
3. the value of the replace must be valid and pointing to an existing CSV version

Tests (manual at this stage)

1. Add the bundle to a copy of the existing index using opm (see upstream e2e tests)
2. Conduct following use-case tests using a catalogsource pointing to the copied index:
   1. Attempt to install a fresh operator
   2. Attempt to upgrade from an older operator
   3. Attempt to install an older operator version (manual approval switched on) using a subscription resource

The tests will not succeed since the operator reference URL is pointing at its public registry (and its not there yet). However, I think mirroring is possible?? But even so the point is if the install gets as far as spinning up a pod with the operator reference then we will have a degree of confidence that the bundle metadata is correct.