RQ cleanup work -- probe script and explicit queue name

[alysivji]

More work getting us ready for Kubernetes.

What does this do

• adding a script to enable us to use probes
• being explicit about the queue name

Callouts

• we are not using the failed queue in a meaningful way

Dependencies

n/a

Resources Used

• RQ docs: Monitoring
• How to probe celery workers
• Kubernetes liveness probes are dangerous
• Google k8s Best Practices: Health checks with readiness and liveness probes

[codecov-io]

Codecov Report

Merging #236 into master will not change coverage by %.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #236   +/-   ##
=======================================
  Coverage   96.05%   96.05%           
=======================================
  Files          68       68           
  Lines        1802     1802           
=======================================
  Hits         1731     1731           
  Misses         71       71           

Impacted Files	Coverage Δ
busy_beaver/app.py	93.18% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f71149d...87f9f9c. Read the comment docs.