kernel-mshv: enable CONFIG_WIREGUARD

[Camelron]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

What does the PR accomplish, why was it needed?
Customer reports they are unable to make this setup work as nodes from node pool(s) created with Workload Runtime set to KataMshvVmIsolation fails as WireGuard expects parameter CONFIG_WIREGUARD to be set and finds it unset at Kernel Level.

Enable CONFIG_WIREGUARD for the kernel-mshv host kernel to address this.

Change Log

• enable CONFIG_WIREGUARD and its dependency CRYPTO modules.

Does this affect the toolchain?

NO

Associated issues

• https://dev.azure.com/mariner-org/container-runtime/_workitems/edit/18336

Test Methodology

• Built manually on a nested kata system.
• MAP build: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1082665&view=results

[romoh]

fixes #16243