chore: combine usages of docker-compose.yml files into a single file

[brianheineman]

While trying to determine how to build the project for the first time I noticed a docker-compose.yml file in the base directory. I assumed this was used to build the project, but it appears(?) that the docker compose files in the docker/ directory are used for that purpose and the one in root is used for pulling/pushing the public images(?). I spent a little time looking at the various docker-compose*.yml files and noticed that they could likely be combined into a single file which might it easier for folks new to the project (but familiar with docker) to reason on. I could be misunderstanding the usage of the files, but I thought a PR might be the easiest / clearest way to communicate my understanding (and have it corrected if mistaken).

I removed the version as I was getting this warning:

I moved docker/run.sh to / and updated it to expect the docker-compose.yml file as a sibling in the same directory; I use RustRover and they have a run option in the gutter of shell scripts; this change makes the script work in this context regardless of the pwd.

I added a default value for ARCH to the build args that works for Mac with ARM processors; which I recall reading you are using(?); if you use x64, you probably want to change the defaults (fwiw, I use a Mac M3). This change allows someone to use docker compose directly without having to go through run.sh.

[epompeii]

Great, thank you @brianheineman!