feat: cargo make + docker for e2e tests

[matthew-hagemann]

Changes:

• Docker & Docker compose to setup and bootstrap test env
• cargo make to manage test lifecycles

To run tests:

• Update local .env, see updated example.env for new variables Docker will need.
• install cargo make: cargo install --force cargo-make
• cargo make full-test

To clean up:

• cargo make full-clean

The rust solution for managing the lifecycle of the server and the tests was becoming way more complicated than just managing through bash, but let me know what you think.

What do you think about how I have structured the docker-compose and the Dockerfiles it calls?
My thinking was to keep the logic for bootstrapping out of the compose file.

The output is quite noisy at the moment with all of the info traces we have. We could look to either not log what happens in the server for the tests, or reduce the number of info traces.