Some dependencies are not catched by the quarkus bom, so it's
necessary to generate and build a project to cache them.

The new automatic test disables all external networking and tries to
generate and build the quarkus project.

Changes:
- There is one unified docker-compose.yml for both repo and sync
- Both containers are started together, but the maven container spins
until the repo is ready
- The repo is terminated when maven terminates
- The repo is set up at port 80 in the container, 9001 on the host
- The maven container is separated from the host network, only has
connections to the repo

From the docker-compose documentation https://docs.docker.com/compose/compose-file/compose-file-v3/#ports:

`docker-compose run ignores ports unless you include --service-ports.`