feat: introduce container-level resource setting

[kondracek-nr]

Description

This change introduces container-level resource-setting to the kubelet & controlplane components. The ksm component already has container-level resource-setting & this change follows the pattern set by ksm. For now, we will continue to accommodate applying resource values set at the kubelet.resources / controlplane.resources level to each container.

If kubelet.resources is set, the assumption is that the user is still using this config path & isn't aware of container-level resource setting, so an explicit setting at this level is prioritized over the default container-level settings this change introduces. We print a warning message that the behavior of that config path will be changing in the future for pod-level resource setting & to use the container-level config paths.

The reason for this change is as follows:

• Currently, when users override the default resources for kubelet or control-plane, the same setting is applied to both containers. Containers may not need the same resource settings - this change allows users to set different resources for each.
• The Windows kubelet DaemonSet currently inherits whatever resources were applied to the Linux DaemonSet. Windows containers often need more robust resources, so it's handy to be able to set these at a different level.
• Pod-Level Resources are coming. The current configuration applies the same resource settings to each container. This change includes a deprecation notice as we will likely want to use the particular configurations kubelet.resources / controlplane.resources in the future to accommodate pod-level resource setting for our customers.

Type of change

• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• New feature / enhancement (non-breaking change which adds functionality)
• Security fix
• Bug fix (non-breaking change which fixes an issue)

Checklist:

• Add changelog entry following the contributing guide
• Documentation has been updated
• This change requires changes in testing:
  • unit tests
  • E2E tests

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.01%. Comparing base (2f7f467) to head (84a9ea5).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1436   +/-   ##
=======================================
  Coverage   75.01%   75.01%           
=======================================
  Files          53       53           
  Lines        3706     3706           
=======================================
  Hits         2780     2780           
  Misses        753      753           
  Partials      173      173           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.