feat: create package bundle for ubuntu 22.04

[supershal]

What problem does this PR solve?:

• Create package bundle for ubuntu-22.04
• ensure that the cloud-init version supported by CAPA is installed. cloud-init_23.1.2-0ubuntu0~22.04.1_all https://github.com/mesosphere/konvoy-image-builder/blob/main/images/ami/ubuntu-2204.yaml#L8
• ensure that latest cloud-init version is installed that is needed for all other providers than CAPA

Which issue(s) does this PR fix?:

• https://jira.nutanix.com/browse/NCN-104852

Special notes for your reviewer:

tested manually and GHA e2e tests will verify this.
ensure that both cloud-init packages are installed.

❯ tar -tvf 1.31.4_ubuntu_22.04_x86_64.tar.gz | grep cloud-init
-rw-r--r--  0 501    dialout  530940 Apr 25  2023 cloud-init_23.1.2-0ubuntu0~22.04.1_all.deb
-rw-r--r--  0 501    dialout  564688 Dec  5 03:13 cloud-init_24.4-0ubuntu1~22.04.1_all.deb
-rw-r--r--  0 501    dialout    4028 Aug 17  2020 cloud-initramfs-copymods_0.47ubuntu1_all.deb
-rw-r--r--  0 501    dialout    6540 Aug 17  2020 cloud-initramfs-dyn-netconf_0.47ubuntu1_all.deb

Does this PR introduce a user-facing change?:

[supershal]

This will add two cloud-init packages in the bundle. one latest and one with this specific version.
Since the package-bundle command is provider agnostic, I think it should be okay to have to version of a packages in bundle instead of adding provider specific logic.

If you are fine with this, I will make the same changes for ununtu-20.04 too in separate PR.
@dkoshkin @faiq

[faiq]

i think we can handle this another way and should probably move away from this sort of pinning altogether

[supershal]

aws e2e offline test for ubuntu-22.02 https://github.com/mesosphere/konvoy-image-builder/actions/runs/12679895399/job/35340712602 🟢