Activate http-proxy-middleware secure flag in production, properly install CA cert instead

[mturley]

We turned off NodeJS TLS validation with this env in the Dockerfile in #186, just as was done in mig-ui, to avoid errors when logging in on some clusters. We should find a better solution.

[mturley]

Equivalent in mig-ui: migtools/mig-ui#1055

[gildub]

This has now migrated to using secure flag for http-proxy-middleware.
See #214 for details.
The question remains to use secure: true for production.
Might not happen before post-beta though.
Adjusted title accordingly.

[mturley]

I forgot about this issue @gildub . I think we actually don't want to use secure at all. In prod, we won't need SSL at all because the internal URLS (http://*.local) don't use HTTPS. And in dev, we'd be forcing the browser to accept self-signed certs anyway, so unless we want to all install the CA cert in our dev environments I think we can safely just use secure: false for developing too (I could be convinced otherwise on that one though).

[gildub]

@mturley, all good then if we don't need SSL between the virt-ui pod and the backend.
Closing this one.

[mturley]

@gildub oops. We should listen to Fabien on this, not me :) #152 (comment)