[Feature Request] Ability to split webserver & worker (or multiple workers) into separate containers

Description I deploy most things on a self-hosted k8s cluster, right now when ingesting a large document, paperless-ngx effectively becomes non-responsive on the webserver. This is bad because with healthchecks and probes configured, it gets killed. I think to enable this setup (and for users with more advanced deployment setups), the following is needed: 1. The ability to disable the webserver service from starting. 2. The ability to disable the worker service from starting. 3. The ability to disable the database migration service from starting, or for the database migration service to not immediately crash when another container is currently performing a migration. Given those 3 options, an example setup I would use would like this: 1 container running webserver/migration 1 container running worker Also, this could potentially enable high availability setups such as: 2 containers running webserver 2-n containers running workers, potentially with autoscaling 2 HAP…