closes #85

Right now, I have a messy docker run script.

Maybe this would be cleaner if I added a new service in the compose file, built from ./Dockerfile, start it with sleep infinity as the command, and docker compose exec into it instead of running a new container every time. We could then use docker-compose for the networking between containers, use depends_on and healthchecks to wait for the db to be up (instead of until psql 'select 1;' do sleep 1; done, and so on.

Problems with current implementation:

• Java parts not working. Need to change docker base image to ubuntu20 - but I prefer if I can fix it through explicitly installing and configuring Java on the official docker python image (Debian)
  • when run locally, complains about unknown hostname - can we change this into explicit localhost?
  • when run on the CI, produces this new error: java.lang.IllegalArgumentException: basedir must be absolute: ?/.ivy2/local
  • can the Java stuff live on a different container in the same docker-compose?
• Assumes/requires UID=1000 on the host. This causes grief on the CI runner where UID=1001
• No idea how to tell pre-commit to run all install/test commands in the container, if possible. Or if we even want that
• rebased on top of ImportError: Package 'textual.widgets' has no class 'TextLog'  #81 pin old version for textual #82 to get some results out of the CI