Skylab suite bots create more swarming tasks and wait for them to finish -- exactly the purpose behind swarm_docker.

This is a mini-project to use swarm_docker for skylab-suite-proxy. The advantanges of doing so are:

- containerize 'em
- in a way other teams in chops do
- includes a way to drain all bots on the server (if setup correctly)
- security implications of running this on our servers.

Doing skylab_suite_proxy first will be a step towards using (modified) docker_devices for skylab-bots (the actual 1:1 mapped to DUT bots).

In this early project we'll figure out how to:

- map /usr/local/autotest and ~/chromiumos checkouts inside the container.
- setup our user and credentials inside the container.

But unlike skyalb-bots, we don't have to figure out how to deal with skylab_inventory, just yet.

https://chromium.googlesource.com/infra/infra/+/HEAD/docker/swarm_docker/
https://chromium.googlesource.com/infra/infra/+/HEAD/docker/docker_devices/

chops' current setup of swarm_docker via puppet (we'd need a similar setup via our puppet code):
https://chrome-internal.googlesource.com/infra/puppet/+/master/puppetm/etc/puppet/modules/chrome_infra/manifests/setup/docker/swarm.pp

public docker pull. (We probably want an internally pinned docker image):
https://chrome-internal.googlesource.com/infra/puppet/+/master/puppetm/etc/puppet/modules/chrome_infra/manifests/packages/docker.pp