Helm Chart OpenShift Route Handling

[Jdubrick]

Please specify the area for this PR
Bug fix and small enhancement

What does does this PR do / why we need it:
This PR aims to address the issue that occurs when a user installs the devfile registry via Helm to an OpenShift environment. Prior to this change the fqdn of the registry-viewer was not properly being set as it was expecting global.ingress.domain to be set, but if you are installing to OpenShift it was not a requirement to set that.

In order to solve this problem the following was added:

1. A helper script for OpenShift installations via Helm

   • This script allows a user to have the fqdn properly set if OpenShift auto generates a domain for you, or if you set a domain yourself. It utilizes Helm Upgrade to mimic the functionality currently in place for the registry operator where the fqdn is set after deployment (it spins up a new replacement pod after the information is known).

2. Template updates

   • In order to have more clarity and consistency, the template used by Helm now has portions for both OpenShift Routes and Kubernetes Ingresses.

3. Updated documentation

   • As a result of changes, documentation was updated to accurately reflect the different ways you can install the devfile registry with the use of a Helm chart.

Which issue(s) this PR fixes:

Fixes devfile/api#1467

PR acceptance criteria:

• Test Coverage
  • Are your changes sufficiently tested, and are any applicable test cases added or updated to cover your changes?

Documentation (WIP)

• Does the REST API doc need to be updated with your changes?
• Does the registry library doc need to be updated with your changes?

How to test changes / Special notes to the reviewer:
The following cases will result in the fqdn of the registry-viewer being properly set:

1. Install to OpenShift with the use of the new script WITH & WITHOUT setting a domain
2. Install to OpenShift using the Helm CLI WITHOUT setting a domain
3. Install to Kubernetes using the Helm CLI WITH & WITHOUT setting a domain

The following case will result in the fqdn not being properly set:

1. Install to OpenShift with the Helm CLI WITH setting a domain

[johnmcollier]

Just a couple small comments

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Jdubrick, johnmcollier

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Jdubrick]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment