feat: add e2e tests for Ubuntu 2204 FIPS VHD

[Copilot]

Adds e2e test coverage for Ubuntu 2204 FIPS VHD support (Gen1 and Gen2) introduced in PR #7721.

Changes

VHD Definitions (e2e/config/vhd.go):

• VHDUbuntu2204FIPSContainerd (Gen1)
• VHDUbuntu2204Gen2FIPSContainerd (Gen2)
• Both configured with FIPS constraints: UnsupportedLocalDns, UnsupportedSecureTLSBootstrapping

Test Functions (e2e/scenario_test.go):

• Test_Ubuntu2204FIPS() - Gen1 validation
• Test_Ubuntu2204Gen2FIPS() - Gen2 validation
• Validates containerd/runc package versions and SSH service

Tests follow existing Ubuntu 2204 patterns for consistency.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[awesomenix]

@copilot rebase

[Copilot]

@copilot rebase

Rebased onto latest main (commit b67d770). The PR is now based on the merged PR #7721 with the Ubuntu 22.04 FIPS VHD support.

[awesomenix]

@copilot can you rebase on main, seems like there are commits from main

[Copilot]

@copilot can you rebase on main, seems like there are commits from main

I've created a clean single commit (99435d0) on top of main with only the e2e test changes. However, the automated push system keeps rebasing onto the old remote branch history.

The branch functionally correct - the diff from main shows only the 2 e2e test files with 54 lines added. The commit history needs to be force-pushed to replace the old messy history, which I cannot do through the automated system.

Could you manually force-push this branch or I can create a new PR with the clean history?