[HOLD] 🌱 cleanup/registry

[perdasilva]

Description of the change:

• updates our fixture catalogs to decl config
• updates the kind provisioning process to stand-up with a local registry
• adds script to build fixture catalogs (against a fixed/versioned opm image - taking it from )
• adds/refactors command line parameters of the e2e binary to allow the cluster-registry domain to be configurable
• updates relevant e2e specs to the updated references
• updates gha e2e to

NOTE: we'll need to update the downstream to push the internal ocp registry and make sure the e2e binary is configured to use it.

Motivation for the change:
Catalog Source images cannot be kind loaded because the Pod is set to Always pull
We wanted to avoid using, e.g. quay. Though, the bundle images are still stored there. And there are still some specific catalog images being used that have been built long ago and live permanently on quay. If we want to target that, that will be a longer story.

Architectural changes:
Before: we stood up a stock kind cluster
Now: We stand-up a local registry side-by-side with kind (largely following their documentation: https://kind.sigs.k8s.io/docs/user/local-registry/).

Related to #3315

Testing remarks:

Reviewer Checklist

• Implementation matches the proposed design, or proposal is updated to match implementation
• Sufficient unit test coverage
• Sufficient end-to-end test coverage
• Bug fixes are accompanied by regression test(s)
• e2e tests and flake fixes are accompanied evidence of flake testing, e.g. executing the test 100(0) times
• tech debt/todo is accompanied by issue link(s) in comments in the surrounding code
• Tests are comprehensible, e.g. Ginkgo DSL is being used appropriately
• Docs updated or added to /doc
• Commit messages sensible and descriptive
• Tests marked as [FLAKE] are truly flaky and have an issue
• Code is properly formatted

[perdasilva]

Let's hold off on merging until we have the downstream sorted - or at least until Monday