1. Proposed title of this feature request
Allow configuration for routes generated by default endpoints (code-redirects) to be HTTPS with TLS edge termination.

2. What is the nature and description of the request?
For workspaces with no endpoints defined in their devfile, a set of default 'code-redirect' endpoints are provided. These endpoints generate non-secure HTTP routes. Cluster administrators following a 'secure-by-default' approach may have HTTP redirects in place at the cluster ingress (or load balancer) level. Currently, this HTTP to HTTPS redirect breaks the resolution of the route, and the developer instead receives the OpenShift "Application is not available" error page. A configurable, say within CheCluster, to allow generated routes to be HTTPS (TLS edge termination) by default will allow cluster configurations with this redirect to have the dynamic convenience of the code-redirect endpoints.

3. Why does the customer need this? (List the business requirements here)
To allow default code-redirect endpoints to function as expected even in secure environments with HTTP->HTTPS redirects.

4. List any affected packages or components.
CheCluster
DevWorkspaceRoutings