Implement Separate Docker Compose Configurations for Development and Production Dockerfiles

[JoblersTune]

Context

To get the best possible developer experience we want to allow for hot module reloading (HMR) in our local playground. Setting this up requires different dependencies and configurations compared to our production environment. This leads to the necessity of having two Dockerfiles: one tailored for development (devDockerfile) and another optimized for production (Dockerfile).

The goal of this task is to create two separate Docker Compose files: one for the development environment that maximizes developer efficiency and ease of use, and another that ensures we can still easily spin up and interact with our production version Dockerfiles.

Linked issues:

• [DevEx] allow for hot reload of backend and auth #2650

Todos

• [ ]