Adding ssl to non-proxy loadbalancer

[jpl-btlunsfo]

Purpose

• Adds back in the SSL configuration, but only applies it to the non-proxy (jpl-internal-only) loadbalancer

Proposed Changes

• ADD ssl certificate ssm reference
• CHANGE current jpl-internal loadbalancer configuration to use HTTPS

Issues

• [New feature] Enforce SSL on SPS endpoints #237

Testing

• Testing in personal deployment
  • currently deployed at https://k8s-sps-airflowi-227d5aa22a-1563308968.us-west-2.elb.amazonaws.com:5000/

[LucaCinquini]

I was able to deploy SPS correctly using this branch, but there are a few issues:
o The terraform output still shows http://.... - this is easily fixable
o The script to deploy the DAGs fails because the SSL certificate is not valid (the certificate hostname does not match the ALB). The solution to this is either to use the top-level proxy to deploy the DAGs, or update the ogc-processin-client with an option to bypass certificate errors

[jpl-btlunsfo]

per your second bullet, I think it would be easier to adjust the OGC api to ignore certificate errors, but I'm not sure which option is best in the long run.