Use a catalogd-defined catalog to install an Operator

[joelanford]

This issue should be closed when a demo recording is posted to the #olm-dev kubernetes slack channel that follows the below script:

Demo Script:

1. Install operator-controller from the main branch or its most recently tagged release using operator-controller's standard install script and manifest.
2. Create a Catalog object referencing quay.io/operatorhubio/catalog:latest
3. Show that the catalog status reflects that it was successfully unpacked.
4. Show that the catalogd metadata api reports objects for all packages, channels, and bundles in the catalog.
5. Create an Operator object referencing package strimzi-kafka-operator.
6. Show that aBundleDeployment is created to reflect a bundle image reference with the highest semver bundle defined in the package (as of 4/5/23, that version is 0.34.0): quay.io/operatorhubio/strimzi-kafka-operator@sha256:42a3dce711492fae22f2d919299a0594f152396f6c2fef65ffc47226ba9c786e
7. Delete the Operator and Catalog objects.
8. Show that no catalog metadata or bundle deployment objects remain.

Related Issues:

• DNR: Wip: Poc/catsrc v2 #141