1. Proposed title of this feature request

Custom Route Name and Certificates for all Service Mesh Components

3. What is the nature and description of the request?
Right now, SM uses cluster certs and static names for all of its components. The default route names for Service Mesh Components do not allow for any level of flexibility in customers environments. The current <name>.apps.<cluster>.<domain> are not user friendly and potentially difficult to remember. Many customers also want to leverage their own certificates for accessible routes.

Ex:
https://grafana-<projname>.apps.domain
https://jaegar-<projname>.apps.domain
https://kiali-<projname>.apps.domain
https://prometheus-<projname>.apps.domain

Similar work was undertaken for the OCP console (https://issues.redhat.com/browse/CONSOLE-2036), but does not account for any other components. There is an OCP RFE to do the same for other OCP components: https://issues.redhat.com/browse/RFE-718

4. Why does the customer need this?

Allows customers to use their own certificates and change the route names to something more meaningful or to adhere to a corporate standard.

5. How would the customer like to achieve this?
The ability to set change one or both of fully custom url and certificates. If no certificates are presented, it should use default certs.

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

Before or as a day 2 operation, it should be possible to modify/customize the route name with a customized url along with the necessary certificates.