Story: As a Quay administrator using the Operator I want to opt out of Operator-based TLS management, so I can rely and re-use OCP-based certificate provisioning and rotation using classic edge based Routes.

Implementation: https://github.com/quay/enhancements/blob/main/enhancements/tls-managed-component.md

Acceptance criteria:

• During default deployments (without user specific configuration) TLS termination is managed by the Route
  • Default Route for Quay must contain its spec.tls.termination field set to "edge".
• Users can still provide their own key and certs (through spec.configBundleSecret)
  • When users provide their own key and cert those must be present in the created Route object.

Test plan:

There is a test plan for this one, it is in https://github.com/quay/enhancements/blob/main/enhancements/tls-managed-component.md#test-plan