Split backend workers into separate containers

> [!NOTE]
> Migrated from [augurlabs/augur#3582](https://github.com/augurlabs/augur/issues/3582)
> Originally opened by `@MoralCode` on 2026-01-15

---

The augur backend container is still sort of a "kitchen sink" container that handles the frontend, the API, and the workers.

Can we split the workers into their own container?

The main usecase I have for this is because I would like to use the `--scale` parameters in docker to simulate/test a more gradual bringup process for the workers. Example:
1. configure augur to have a really low worker count for each task (like 1-2 for each of core facade and secondary
2. start augur with one worker.
3. use the --scale flag to bring up multiple instances of the worker container, each running a set of workers with these combined low limits, but spaced out over time to watch memory use patterns in grafana

im still seeing some concerning memory use patterns even when running from 8ec768dac20841db1f625d3b3b0c154ad88dec4f.