feat: Support creating Ubuntu 22.04 OVA (vSphere) image

[dlipovetsky]

What problem does this PR solve?:
Adds support for creating an Ubuntu 22.04 OVA (vSphere) image.

Which issue(s) does this PR fix?:

• https://jira.d2iq.com/browse/D2IQ-NUMBER

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

[dlipovetsky]

We created Ubuntu 20.04 images recently: https://github.com/mesosphere/konvoy-image-builder/actions/runs/10549643236/job/29224908365

[dlipovetsky]

The e2e tests, which provision an image, but do not create a snapshot, passed, with once exception: Ubuntu 22.04.

    vsphere-clone.kib_image: TASK [packages : install apt-transport-https deb package] **********************
    vsphere-clone.kib_image: FAILED - RETRYING: [default]: install apt-transport-https deb package (3 retries left).
    vsphere-clone.kib_image: FAILED - RETRYING: [default]: install apt-transport-https deb package (2 retries left).
    vsphere-clone.kib_image: FAILED - RETRYING: [default]: install apt-transport-https deb package (1 retries left).
    vsphere-clone.kib_image: fatal: [default]: FAILED! => {"attempts": 3, "cache_update_time": 1726520746, "cache_updated": true, "changed": false, "msg": "'/usr/bin/apt-get -y -o \"Dpkg::Options::=--force-confdef\" -o \"Dpkg::Options::=--force-confold\"       install 'apt-transport-https=2.4.13'' failed: E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 3071 (unattended-upgr)\nE: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?\n", "rc": 100, "stderr": "E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 3071 (unattended-upgr)\nE: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?\n", "stderr_lines": ["E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 3071 (unattended-upgr)", "E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?"], "stdout": "", "stdout_lines": []}
    vsphere-clone.kib_image:
    vsphere-clone.kib_image: PLAY RECAP *********************************************************************
    vsphere-clone.kib_image: default                    : ok=24   changed=11   unreachable=0    failed=1    skipped=153  rescued=0    ignored=0

It looks like something acquires the dpkg lock in the background while ansible is running. A known upstream issue is a conflict with Ubuntu's automated, period upgrades: ansible/ansible#51663

[dlipovetsky]

I'm going to pull the apt fix into its own PR; we'll need to backport.

Update: #1177

[dlipovetsky]

Running vsphere-air-gapped with ubuntu-2204 template: https://github.com/mesosphere/konvoy2/actions/runs/10929457951

Update: passed! https://github.com/mesosphere/konvoy2/actions/runs/10929457951/job/30340520536