Route TLS Fixes for Security Scanner (PROJQUAY-1091)

[alecmerdler]

Issue: https://issues.redhat.com/browse/PROJQUAY-1091

Changelog: Switch to always passthrough TLS for Route and generate cert/key pair if not provided.

Docs: N/a

Testing: TODO(alecmerdler)

Details:

We cannot use edge TLS termination with OpenShift Routes because there is not an easy or reliable way of retrieving the cluster CA that is used by the Ingress Operator when it creates Routes. This is a problem because Clair needs to trust the HTTPS of whatever storage backend it is fetching image layers from. Instead, we switch to always terminating TLS at the Quay container (which is preferred anyway) and generating a cert/key pair if the user does not provide them in their configBundleSecret.

• Remove edge TLS termination for Quay Route and only allow passthrough targeting the https port
• Ensure FEATURE_PROXY_STORAGE is enabled and we are using s3.openshift-storage.svc and injecting service-ca.crt to Quay and config-tool Deployments
• Generate ssl.key + ssl.cert if not provided

Reverts work done in: #320 and #315