Add initial operatorhub templates

[tylerauerbeck]

What is this PR About?

This adds some initial templates for interacting with OperatorHub. This assumes that OLM is running and configured appropriately.

How do we test this?

Test by deploying the Elasticsearch operator on OCP 4:

oc new-project my-namespace

oc process -f operatorgroup.yaml -p NAME=openshift-logging-operatorgroup -p TARGET_NAMESPACE=my-namespace| oc apply -f - -n my-namespace

oc process -f catalogsourceconfig.yml -p NAME=elasticsearch-operator -p OPERATORS="elasticsearch-operator" | oc apply -f - -n openshift-marketplace

oc process -f subscription.yaml -p NAME=elasticsearch-operator -p OPERATOR_NAME=elasticsearch-operator -p OPERATOR_NAMESPACE=openshift-operators -p CATALOG_SOURCE_NAME=elasticsearch-operator | oc apply -f - -n openshift-operators

cc: @redhat-cop/day-in-the-life

[pabrahamsson]

Looks good @tylerauerbeck, two minor comments inline.

[pabrahamsson]

I think this line should be removed and instead set the namespace from cli or from the applier.

[tylerauerbeck]

@pabrahamsson Fixed. Let me know what you think.

[pabrahamsson]

LGTM