variants: add k8s-1.32 variants boilerplate

[Sparksssj]

Issue number:

Part of #4318

Description of changes:

Add the boilerplate for upcoming new k8s-1.32 variants of Bottlerocket.

Testing done:

Draft until a core kit is released that includes bottlerocket-os/bottlerocket-core-kit#298 . Once that core kit is released and Bottlerocket is updated to use it, will rebase this PR and open for review. For testing these changes, I used a custom built bottlerocket-core-kit.

For testing:

• cargo make -e BUILDSYS_VARIANT=vmware-k8s-1.32 -e BUILDSYS_ARCH=x86_64
• cargo make -e BUILDSYS_VARIANT=aws-k8s-1.32 -e BUILDSYS_ARCH=x86_64
• cargo make -e BUILDSYS_VARIANT=aws-k8s-1.32-nvidia -e BUILDSYS_ARCH=x86_64
• cargo make -e BUILDSYS_VARIANT=aws-k8s-1.32 -e BUILDSYS_ARCH=aarch64
• cargo make -e BUILDSYS_VARIANT=aws-k8s-1.32-nvidia -e BUILDSYS_ARCH=aarch64

Launched the aws-k8s-1.32-aarch64 variant and ensured it booted and registered w/ k8s cluster.

Terms of contribution:

By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.

[vigh-m]

So, the new setting being added in PR #4345 is currently set to default to false for all k8s variants. We're splitting this behaviour for k8s 1.31 and below and want this to default to true starting k8s 1.32 onwards.

To support that, we will need a new settings-defaults package for aws-k8s-1.32 and a new sources/shared-defaults/kubernetes-device-ownership-default-true.toml with content similar to below, symlinked into the aws-k8s-1.32 settings-defaults folder:

[settings.kubernetes]
device-ownership-from-security-context = true

[metadata.settings.kubernetes.device-ownership-from-security-context]
affected-services = ["containerd"]

[vigh-m]

⬆️ Pushed changes to enable the device-ownership setting for k8s-1.32

[vigh-m]

⬆️ Push after rebase and adding new defaults for -nvidiaand vmware variants

[vigh-m]

⬆️ Updated the commit message

[yeazelm]

Is this intended?

[vigh-m]

I think so. There is an extra \s on those lines not present elsewhere. Probably got cleaned up by a linter