Fix the self-signed TLS/SSL certificate issues

[jwalcorn]

Right now, whenever you try to load the Stock Trader UI in a browser, there's this embarrassing dialog about the TLS/SSL certificate making the site look dodgy, and the browser recommends not loading the page, and you have to click the button to let me in anyway.

This is due to the self-signed certificate that Stock Trader uses.

This wasn't an issue back when we ran on OpenShift, as it used Routes to expose a UI to a pod, and those had this cool built-in feature to generate and use Let's Encrypt issued certificates, so the browser was happy. But we lost that when we left IBM and started mostly working with AKS and EKS (and presumably GKE). The route did SSL termination, and "proxied" the call on to the pod as needed. One option for addressing this is to manually implement a similar solution.

Another might be to use https://cert-manager.io, which is a Kube-native way to deal with TLS/SSL certificates. And I believe that most of the service meshes (like Istio) have built-in support for cert-manager, so maybe embracing a service mesh (which would have lots of other benefits, of course) is the answer?

This is also a bigger issue with my (still under construction) native iOS app:

The SwiftUI framework both won't allow plain http, and when you use https it won't allow self-signed certificates (or otherwise problematic certificates, like ones that are expired, or say they are for a different domain, or whatever). I had to jump through some hoops (that would probably disallow my app from ever being available in the iOS App Store) to get around that.

Anyway, we need to figure out a solution to this certificate issue, as https is a reality, and a proper certificate is key to making that work.