Automated testing and docker-compose.yml overhaul

[aaron97neu]

Previous discussion: #45 (comment)

Currently our docker-compose.yml files are chained together with a docker-compose -f ... -f ... -f .... command to bring up a series of containers for manual testing. We would like each docker-compose.yml file to be self-contained and (eventually) run automated tests when brought up (Maybe a separate docker-compose-testing.yml?)

For service xxx the docker-compose.yml should have the following properties:

• When in folder isoblue-avena/services/xxx, docker-compose {build up down etc} should work
• Any dependent containers are not build from adjacent folders but the latest good version pulled from dockerhub (which is automatically updated via github actions)
• Ability to run automated tests on this container

@abalmos This is your vision. Any other comments?