Support serving the front end in HTTPS

[JosephMarinier]

Description:

• Support serving the front end in HTTPS
• Stop exposing the back end's port in docker-compose.yml and have the front end call the back end using Docker Compose's internal network. So, when using Docker Compose (make launch), the back-end API will only be accessible through the front-end proxy (for example, the Swagger UI will be at http://localhost:8080/api/local/docs). This way, if you use HTTPS to secure the front end (by setting env vars HTTPS_KEY and HTTPS_CERT), the back end will be secured too.

This will be an undocumented "beta" feature for now, until we use it a little bit and make sure it is useful in this state.

Checklist:

You should check all boxes before the PR is ready. If a box does not apply, check it to acknowledge it.

• ISSUE NUMBER. You linked the issue number (Ex: Resolve #XXX).
• PRE-COMMIT. You ran pre-commit on all commits, or else, you
  ran pre-commit run --all-files at the end.
• USER CHANGES. The changes are added to CHANGELOG.md and the documentation, if they impact
  our users.
• DEV CHANGES.
  • Update the documentation if this PR changes how to develop/launch on the app.
  • Update the README files and our wiki for any big design decisions, if relevant.
  • Add unit tests, docstrings, typing and comments for complex sections.