Make ports exposed in docker compose configurable

[relud]

docker-compose is exposing ports on the host that I believe are only needed internally within the docker-compose network.

This caused me issues with trying to use a vscode devcontainer, as seen in mozilla-services/tecken#2857, because both projects expose these ports, and the environments are not automatically shut down when vscode is closed: https://github.com/mozilla-services/tecken/pull/2857/files#diff-24ad71c8613ddcf6fd23818cb3bb477a1fb6d83af4550b0bad43099813088686R10

It would make sense to also do this in tecken, but that exposes more ports that I am less sure are unnecessary

see also mozilla-services/tecken#2858

per https://github.com/mozilla-services/tecken/pull/2857/files#r1430382049

 "shutdownAction": "none",

[biancadanforth](https://github.com/biancadanforth) [Dec 18, 2023](https://github.com/mozilla-services/tecken/pull/2857/files#r1430382049):
This is what prevents the devcontainer from shutting down when we close out of VS Code IIUC.

with devcontainer and its docker-compose dependencies running even when vscode isn't open, ports conflict between tecken, eliot, and socorro, so this PR makes the exposed ports configurable via environment variables, which can be set in .env in each project to avoid overlap.

[willkg]

We use a lot of the same services between Antenna, Eliot, Socorro, and Tecken. I can't remember if I did a good job of making them consistent. If they're not consistent, we should fix that--but we could do that in the future.

[willkg]

If you set this in .env, then make run doesn't really work. Is it possible to set this in .env for the local dev environment, but not the devcontainer?

[relud]

then make run doesn't really work

how so? it still runs eliot, just exposed on a different port

[willkg]

Once we add the .devcontainer stuff, we should adjust the stop rule in the Makefile to something like:

.PHONY: stop
stop: .env  ## | Stop docker containers.
	${DC} -f docker-compose.yml -f .devcontainer/docker-compose.yml stop

We might also want to write up a page in Confluence covering using VSCode with all the crash ingestion services.

This looks good!

[smarnach]

We could put the configuration for the dev container in the main docker-compose.yml file. I chose to put it in a different file to keep things separate, but I don't know how much value there is to keeping things separate. If we merge the configuration files, managing the dev container from the command line will become easier.