Refactors docker compose file setup

[skrawcz]

This structure more naturally fits what docker expects. A docker-compose file at the root, with docker files for the respective services in those modules.

I have tested this locally for the prod build
and pushed things and I believe it works for
the other cases too.

TODO:

• dockerx build instructions
• automating the build & versioning of images with new releases

Changes

• move docker files around

How I tested this

• locally

Notes

Checklist

• PR has an informative and human-readable title (this will be pulled into the release notes)
• Changes are limited to a single goal (no scope creep)
• Code passed the pre-commit check & code is left cleaner/nicer than when first encountered.
• Any change in functionality is tested
• New functions are documented (with a description, list of inputs, and expected output)
• Placeholder code is flagged / future TODOs are captured in comments
• Project documentation has been updated if adding/changing functionality.

[skrawcz]

@flavour thoughts?