Connector performance test infrastructure setup tasks remaining

[theotherian]

We're using this to track what we have left to do on our performance test infrastructure setup now that we at least have a pulse to the silly thing.

• Pass variable for simulation from scheduler to pubsub to function to vm
• Name container used for running load tests and add docker wait command to block until complete
• Add auto deletion to vm that is created from scheduler
• Add additional parameters to simulation that allow control of users/ramp/etc via arguments passed to the docker run command
• Find out if it's ok that this exists in the java-connector-test project or if it should exist in Xpring Sandbox (probably the latter)
• Better interface to look at reports (nice to have)
• Set up additional connectors for different topology tests
• Make sure having a public storage bucket for load test results doesn't create other issues we're not aware of
• Documentation of resources and approach
• Get output of load test into gcloud logging

[theotherian]

Closing out this ticket as all of these are set up except for 1. We also have a few bugs that have been captured as well.

Here are the associated tickets:
interledger4j/ilp-performance#8
interledger4j/ilp-performance#7
interledger4j/ilp-performance#6