Get E2E tests running in DooD scenarios

[jellyDean]

Currently E2E tests are not being ran in VSTS/CI. This task is the second of two the first being getting E2E tests running in condo. After getting the E2E tests running in condo this is what needs to be done.

• Investigate VSTS server. Identify needed dependencies to run docker and e2e tests. Also investigate how condo.sh is ran on it and figure out a way to reproduce that via command line
• Release a build (tarball) of condo that has e2e tests supported. Do not need to follow CI strat yet. This is just a proof of concept.
• Take the E2E condo tarball and scp it up to the VSTS server
• Take a micro service that uses condo i.e. campaigns service and scp it up to the VSTS server as well
• Run the tests in the that microservice with condo tarball. Figure out any problems and sort them out
• Release an new version of condo by merging your fork in. Follow proper CI strat thats in place. Make sure a release is drafted so that condo.sh can pull it down
• Do a PR on a microservice that uses E2E tests and watch them pass or fail. If they fail figure out way
• Lastly document everything that is being done so someone can understand how this was done

[dmccaffery]

VSTS build agents include DooD and the docker CLI OOB -- we should support all DinD and DooD via #49. I'm going to rename this to "Get E2E tests running in DooD scenarios".

Couple of other things:

VSTS is a cloud platform solution; not a "server" -- we cannot SCP to it. Use the --branch argument against a separate branch to run the test scenarios in our VSTS build process as normal. The argument is already supported by the build task group we use for condo on both Windows and Linux.