Investigate RQ docker image issue on production

[maxsibilla]

The new process for deploying on production is to build main on vm05 and push the image to Dockerhub then pull and run on vm06. Currently the Ingest API image does not wrap the RQ service docker image so when deploying using the shell script it needs to build the rq service. Additionally there are errors when attempting to run a job (e.g. data-status for datasets and uploads).

Potential solution is to wrap the rq service docker image into Ingest API's image or build and push that separately.