Improve roachprod --geo flag for easier geo-distributed testing

[awoods187]

Roachprod --geo doesn't work with AWS:

roachprod create $CLUSTER -n 4 --clouds=aws  --aws-machine-type-ssd=c5d.4xlarge --geo
Error: accepts 1 arg(s), received 0

On GCP, roachprod will create a 4 node cluster the doubles up n1 and n2:

Andrews-MBP-2:~ andrewwoods$  roachprod create $CLUSTER -n 4 --gce-machine-type=n1-standard-16 --geo
Creating cluster andy-optzc with 4 nodes
OK
andy-optzc: [gce] 12h52m34s remaining
  andy-optzc-0001	andy-optzc-0001.us-east1-b.cockroach-ephemeral	10.142.0.159	35.229.126.6
  andy-optzc-0002	andy-optzc-0002.us-east1-b.cockroach-ephemeral	10.142.0.160	35.231.169.191
  andy-optzc-0003	andy-optzc-0003.us-west1-b.cockroach-ephemeral	10.138.0.31	35.230.95.249
  andy-optzc-0004	andy-optzc-0004.europe-west2-b.cockroach-ephemeral	10.154.0.31	35.234.156.121

This is problematic because we now need to point workload at n2 rather than n4 to get the geo-distributed cluster we desire. Note, if you point it at n1, then roachprod start won't work because it expects the cluster to be kicking off from n1.

Here is how you are forced to test with --geo:

roachprod create $CLUSTER -n 4 --gce-machine-type=n1-standard-16 --geo
roachprod run $CLUSTER --  "DEV=$(mount | grep /mnt/data1 | awk '{print $1}'); sudo umount /mnt/data1; sudo mount -o discard,defaults,nobarrier ${DEV} /mnt/data1/; mount | grep /mnt/data1"
roachprod stage $CLUSTER:1,3-4 cockroach
roachprod stage $CLUSTER:2 workload
roachprod start $CLUSTER:1,3-4
roachprod adminurl --open $CLUSTER:1
roachprod run $CLUSTER:1 -- "./cockroach workload fixtures import tpcc --warehouses=2500 --db=tpcc"

[awoods187]

While we are at it, I'd like to be able to use the node map too which appears to require adding information to systems.locations

And the drill down: