Add torque to the development environment

[slifty]

Oh the irony!

Torque itself is not actually part of this development environment. It's used in it, but only in the sense that ansible downloads it and sets it up in competitions.

We may want to do something like what we do with SimpleBook, where we run the Ansible scripts which would be used to power production, but ultimately delete the "ansible checked out" copy on the guest machine and replace it with a mounted copy.

If / when we do this we would want to consider wrapping torque in gunicorn similar to how we do on SimpleBook. This lets us do things like trivially restart torque when code changes.

[frankduncan]

Be aware that now torque spawns a background thread that does cache rebuilding (in the postgres branch, which will get merged to main probably before this is handled). Whatever you end up doing, make sure that you are restarting the whole service on code changes. The development environment naturally just restarts the web part of the service.