Custom Docker repository names

[peterfelts]

NOTE: this PR will show > 1K files until #36 is merged

This change will enable Device Simulation to pull custom images from a specified Docker Hub account. Before this change, when a Simulation VM booted up, the VM would start Docker and pull images from a hard-coded repository name. Now developers will be able to specify a custom repository name to have Simulation pull images from.

The flow is:

1. (optional) make code changes to any of the Simulation microservices
2. Run BuildAndPush.cmd, providing a Docker image repository name and an image tag
3. Add the image repository name and the image tag to the deployment configuration
4. Run npm run deploy from the deployment folder
5. The Azure cloud resources necessary to run Device Simulation will be deployed to Azure
6. An Azure VM will boot up and start Docker Compose
7. Docker Compose will pull down the images specified in config (step Add diagnostics submodule to project and service endpoint to nginx #3)