kubernetes: add fail-cgroup-v1 setting

[ytsssun]

Issue #, if available:
bottlerocket-os/bottlerocket#4725

Description of changes:
Add fail-cgroup-v1 setting to support Kubernetes 1.35+ variants.

Kubernetes 1.35 enables failCgroupV1=true by default in kubelet, causing it to refuse starting on cgroup v1 nodes. While Bottlerocket defaults to cgroup v2, users who have opted into cgroup v1 via
settings.boot.init.systemd.unified_cgroup_hierarchy=0 will need a way to override this behavior.

This adds a new boolean setting:

[settings.kubernetes]
fail-cgroup-v1 = false

This allows users on cgroup v1 to continue running while they plan their migration to cgroup v2.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[koooosh]

We still need to bump the version here, right?

[ytsssun]

We still need to bump the version here, right?

I was planning on doing that in the release PR, but I guess I can make them a single PR given the size of the diffs.

[ytsssun]

Added changelog and bumped the model versions.

[ytsssun]

Force pushed to address comments from @KCSesh. Basically added alias to the setting.

[KCSesh]

LGTM

[ytsssun]

Tested the alias -

[root@admin]# sheltie
bash-5.1# apiclient get settings.kubernetes.fail
{}
bash-5.1# apiclient set settings.kubernetes.fail-cgroupv1=false
bash-5.1# apiclient get settings.kubernetes.fail
{
  "settings": {
    "kubernetes": {
      "fail-cgroup-v1": false
    }
  }
}
bash-5.1# apiclient set settings.kubernetes.fail-cgroup-v1=false
bash-5.1# apiclient set settings.kubernetes.fail-cgroup-v1=true
bash-5.1# apiclient get settings.kubernetes.fail
{
  "settings": {
    "kubernetes": {
      "fail-cgroup-v1": true
    }
  }
}
bash-5.1#