Ensure that Noctua-in-AWS is HTTPS-only

[kltm]

Currently, Noctua-in-AWS runs as both HTTP and HTTPS (initial intentions).

We now understand a little more about how this will have to work practically and want to ensure that the apache proxies do HTTPS-only, with HTTP forwarding to appropriate scheme (as is usual for most sites).

[kltm]

It looks like @mugitty has gotten most of them, but I just noticed that http://3.226.81.154/ at barista runs in the clear. We'll need to clear this one up too.

[kltm]

While most of the work has been completed by @mugitty here, because we cannot mix http and https and our current NEO (autocomplete) is HTTP-only, we'll need to setup a new AmiGO/GOlr with NEO that is HTTPS-friendly. Ideally, with repeatable devops.

I attempted doing this with the current state of the AmiGO provisioning, but didn't get quite far enough. For my next attempt, I'll be using terraform for provisioning the instance, then filling it in with the older ansible devops (which should be faster to debug).