Re-introducing the ability to connect to a VM outside of the pool.
I know we had planned to postpone this, but I think re-introducing
it now is a good idea, because
1. I don't want to connect to the VM pool while the NFS-mounted
software server is broken (ephemeral disk corruption).
2. I think the main reason for disabling this functionality
previously was because it was confusing using the same field
on the CVL tab for 2 different purposes (a "connection profile name"
and a "hostname/IP address"), but this has been solved now by
splitting the connection and login host into two separate fields.
3. I need to give Huygens users access to the Huygens Test server
for User Acceptance Testing of the CVL-integrated Huygens solution.
We could use a "Huygens Test" queue for this, but I don't like
having to hard-code this new queue name into the Launcher when
it is only likely to be used by a small number of users over a
short period.  It seems nicer to allow them to paste in an
IP address.
4. Jupiter has asked a few times recently whether he can use
the Launcher to connect directly to a VM for testing stuff
before it goes into the official pool.
5. Anna has requested the ability to connect directly to a
VM outside of the pool.