Set up an e2e-vsphere job akin to the existing e2e (AWS), e2e-gcp, and e2e-azure.

It should be optional, run automatically only if the PR touches files with vsphere in the name (or obvs if run explicitly).

Discussed with vsphere and DPP folks, the strategy will be:

• Use the vsphere workflows to provision the hub. (This gets the hub inside the twingate VPN so our job doesn't have to worry about tunneling.)
• The job setup (the bit that's in the commands) needs to pre-provision the DNS entries for API and apps and add those provisioned IPs to the teardown JSON so they get cleaned up when the job terminates.
• Our e2e script needs to grow a vsphere code path, including a way to receive all the vsphere-specific parameters we need.