this allows different hosts (jump hosts) to have different identity files
specified

as per commit from MaxMatti:
dmacvicar@1152bdd

allow querying VM Host capabilities so that we can make decisions on what
resources to deploy. This can be things like machine architecture, but possibly
also to deploy VMs in a CPU topology manner

however tests aren't running right project wide and there will need to be a PR
to address this

provider now only stores the default URI but does no book-keeping of its own,
instead the Client class is used to manage provider connections

the lock is acquired after two calls to retrieve the volume pool and key. While
this is a potential slow down in those events where either one isn't found, it's
probably not a problem to be concerned about.

1. remove the lock management from the cloudinit_def as this is an abstraction
leak (also, the lock is acuqired very early in the call and has no performance
penalty unless there is a lookup failure)
2. fetch local `host` value when obtaining a connection or use default provider
URI instead if not found

1. move lock ownership to upper layer
2. obtain network connection on each action

if we are connecting to multiple servers for simulatenous creation of volumes,
there's no need to do this sequentially across all servers

the hostKeyCallback makes use of the SSH port and fails if a custom ssh port is
being used by the host

this value was chosen as the lowest RSA available by default on a debian build
running OpenSSH_9.2 and works out of the box for most hosts tested by authority.
Any older systems can specifically set their key algorithms in .ssh/config

provider now only stores the default URI but does no book-keeping of its own,
instead the Client class is used to manage provider connections

the lock is acquired after two calls to retrieve the volume pool and key. While
this is a potential slow down in those events where either one isn't found, it's
probably not a problem to be concerned about.

1. remove the lock management from the cloudinit_def as this is an abstraction
leak (also, the lock is acuqired very early in the call and has no performance
penalty unless there is a lookup failure)
2. fetch local `host` value when obtaining a connection or use default provider
URI instead if not found

1. move lock ownership to upper layer
2. obtain network connection on each action

…virt into production

Add none option to graphics

This reverts commit 401c36c.