Use TLS re-encryt instead of edge termination in Fuse console route

For the time being, the communication between the Fuse console and the OpenShift cluster relies on edge termination, which means that the communication is secured from the browser to the OpenShift master, but not within the cluster, from the master to the services / pods.

As an administrator, I want to be able to deploy the Fuse management console, with end-to-end encryption configured by default in the console templates, so that the console end-users requests are secured end-to-end, from the browser to the in-cluster services.