Use valid Windows Server 2022 image in platform=none job

Description

This story covers using a WS 2022 image in the platform=none CI job.

The WS 2022 image that we use in the vSphere IPI job cannot be reused for platform=none. The behavior we are seeing is that, after installing the networking OS patch on a WS 2022 template, any CI job that uses the UPI vsphere workflow (including the wicd-unit test job) will be unable to establish an SSH connection with instances created from that template. The VMs are SSH accessible from the bastion host though. SPLAT thinks the machine IPs in failed jobs look strange – this may be an issue with our the way we handle excludeNics in the VMWare tools.conf. 

Acceptance Criteria

• working template is present in vmc vCenter and replicated to IBM environment
• platform=none job points to 2022 template in release repo
• 2022 template should have docker installed (since the same template is used across all branches, we need to be compatible with older releases that don't have containerd support)
• all e2e tests pass