Use docker containers to launch load test commands instead of child spawn

Currently we just fork a process to run a load test tool, however this is troublesome as the dependencies of benchmark-controller is tied with the load test tool as we just create one docker image.

We should instead allow the load test tool to be packaged in a separate docker container, and we launch through docker in the benchmark controller instead.