Put devfile registry operator to OperatorHub

[elsony]

/kind user-story
/kind epic

Which area this user story is related to?

/area registry
/area releng

User Story

As a developer working on the integration of the devfile registry service in another project, I want to have the devfile registry operator available on the OperatorHub, so that I can receive stable releases of the registry operator from an official source for my projects devfile registry deployments.

Before we can make the operator available in the catalog, we will need to stabilize it first. We made some major changes in the last few months to migrate the operator to newer k8s dependencies and re-worked the way the registry viewer gets deployed but it's caused some issues that we are still working through. Once things are stabilize, we will need to ensure we have processes and test coverage to ensure we can update on a regular basis.

These are some of the considerations that will apply to both artifacthub and operatorhub:

1. We will need to come up with a release process. Currently one does not exist but once we cut one, we will consider releasing on a regular cadence TBD (either per quarter and/or driven by dependency updates whichever comes first). Our plan is to support openshift 4.12+ in our first release

2. We need to ensure there's additional testing before publishing to the catalogs. e.g. we do not have tests for the OLM bundles and we don't have integration tests with openshift. We will probably need to add tests for Eclipse Che since they are another client that is interested in using the operator

3. Ensure helm chart and operator are consistent. Currently they are out of sync

Issue revised by: @michael-valdron
Originally defined: #1007 (comment) by @kim-tsao

Acceptance Criteria

• Registry operator host alias for registry viewer not working #1028
• Registry operator should be in sync with operator SDK releases #1106
• Devfile registry operator pre-release to OperatorHub #1211
• Publish registry operator to OpenShift OperatorHub #1301
• Complete documentation coverage of registry operator #1015
• Automatically publish registry operator release images #1267
• Create and define a release process for registry operator #1194
• Update CONTRIBUTING for registry operator #1233
• Registry operator OLM tests not passing #1251

Removed Criteria

• Spike: Investigate what is needed for registry operator and helm chart consistency #1193
• Remove deprecated APIs from registry operator #1195
• Add testing for registry operator OLM bundles

[johnmcollier]

Instructions on adding a community operator to OperatorHub can be found here: https://operator-framework.github.io/community-operators/

Required fields within your CSV also provides some good information on what the CSV (ClusterServiceVersion) in the Operator's OLM bundle needs to contain