Update docker-compose.yml to use a specific release

[yanokwa]

Consider pinning docker-compose.yml to a specific release and pinning docker-compose.dev.yml to master so pre-releases are dogfooded.

[florianm]

Would you be happy to leave docker-compose.dev.yml at :latest which should be the latest master?

Side thought, how about a release issue template with a step by step release process?

[yanokwa]

I believe "latest" is the latest release and "master" is master. Sounds like we both want master, correct?

[florianm]

"latest" is the latest build without an explicit docker tag or with the tag "latest". Since the ghcr.yml GH action pushes only the tag "master" and not "latest" (see https://github.com/getodk/build/pkgs/container/build/versions), you are right that docker-compose.dev.yml should tag "master" and docker-compose.yml should tag the latest tagged release.