Setup infrastructure for containerized tool execution for insecure tools.

[jmchilton]

Someday we should be running all tools this way, and when we have to disable tools for security problems it would be good to have a Dockerized destination we could send them to in order to keep them in the tool panel.

• SLURM worker node needs to have a Docker service running.
• Add <param id="docker_enable">True</param> to the destination for the tool.
• Use <param id="docker_container_id_override">XXX</param> to hardcode the image ID at first to use for the tool - the images will likely all exist on quay.io. Longer term we can let Galaxy find the image ID from the requirements but this reduces potential problems until we get things robust and running.

Alternatively we could use Singularity. I can provide instructions for that as well.