Devfile registry operator pre-release to OperatorHub

[michael-valdron]

Which area/kind this issue is related to?

/area registry
/area releng

Issue Description

In #410, we plan to make our first release of the registry operator available on OperatorHub for consumers. To ensure early adopters are ready to ship when this release becomes available, it would be necessary to also provide pre-releases.

Resolve #1106 to ensure no problems with publishing.

Acceptance Criteria

• Required documentation for publication https://k8s-operatorhub.github.io/community-operators/packaging-operator/#provide-information-about-your-operator
  • What the managed application is about and where to find more information
  • The features of your Operator and how to use it
  • Any manual steps required to fulfill pre-requisites for running/installing your Operator
• Cut pre-release number for registry operator
• Ensure bundle files are up to date and placed under the following directory structure within a folk of k8s-operatorhub/community-operators: https://k8s-operatorhub.github.io/community-operators/packaging-operator/#create-a-release
• Create a PR of these change to the folk within the k8s-operatorhub/community-operators repository and merge once approved

[michael-valdron]

Cut pre-release number for registry operator

I think we should start with 0.1.0, increment on minor until our first release 1.0.0.

[michael-valdron]

Add minimal documentation for publication to OperatorHub

[michael-valdron]

Add minimal documentation for publication to OperatorHub

Documentation acceptance criteria has been included.

[michael-valdron]

Begun prep work for pre-release. Updated maintainers, CR descriptors, and set version fields to 0.1.0.