Update e2e-resources and e2e for local Windows testing

[TmNguyen12]

Description

This PR adds several resources to the e2e-resources chart that deploy onto Windows-based nodes (Windows Server 2019 & Windows Server 2022) when enabled.

Resource types include

• deployment / replicaset
• statefulset
• cronjob
• daemonset
• failing jobs

It also includes e2e tests meant to run locally, separately from the standard e2e tests. Our current automated e2e tests run using Minikube, which does not support Windows nodes, so we follow the basic local test script pointing at a different exceptions file & specs file for Windows. Automating this will be a little involved, and will come later.

Note that several tests present for Linux are not present for Windows due to known limitations in available metrics (eg most netTx/netRx/netErrors), tests that are not relevant for Windows (anything to do with cpuCfs), & some that I haven't looked into yet (PVC, container pending). This should cover the bulk of the tests, though.

Known issues:

• Until the PR updating the nri-kubernetes helm chart is merged, the main integration must be installed separately from the windowsUpdateHelmChart branch.
• I don't like the way I've laid out the 2019 vs 2022 tests, but it should do for now.
• There are only exceptions files for 1.29 & 1.32, as we do not currently have canaries for other k8s versions
• Resource requests/limits are fairly high for the new Windows resources. Powershell won't run on the resource requests/limits we had in place for linux-based resources (too low), but we could probably tune these requests down further.

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

[dbudziwojskiNR]

Sorry to keep nit picking on this, but can we not use tolerations here? Really trying to avoid baking in new config options that we'll end up needing to support in the future. If the plan is to drop theses keys in a follow up PR because we're currently testing Windows, I'm okay with this. Just checking.

[kondracek-nr]

i'd like to keep the option in e2e-resources because we might not always want to deploy resources for windows. is there an expectation that we need to support e2e-resources for customers?

[dbudziwojskiNR]

I get that, but wouldn't the windows resources not deploy anyways due to tolerations? I don't think we do need to have customer support on this, it's more that I think we should minimize configs that may be "redundant".

[TmNguyen12]

because they are deployments they deploy and are stuck in pending because they cant' find a node.

if they were daemonsets they would not deploy

[kondracek-nr]

only if the cluster the user is deploying e2e-resources to doesn't have windows nodes! our canaries, for example, have a windows node by default, so it's possible someone's just trying to test something real quick in linux nodes. i'd rather have more levers to pull to target testing, like we do with whether or not we want deployments/statefulsets/daemonsets in general.