Add support for Container insights on Windows

[KlwntSingh]

Description:
This PR adds CI on Windows feature in awscontainerinsightsreceiver. This PR merges dev branch aws-ci-windows into aws-ci-dev

Ex. Adding a feature - Explain what this achieves.-->
This PR adds CI on Windows feature in awscontainerinsightsreceiver.

Testing:

1. Unit tests pass for Windows

ok      github.com/open-telemetry/opentelemetry-collector-contrib/receiver/awscontainerinsightreceiver/internal/k8swindows      (cached)
ok      github.com/open-telemetry/opentelemetry-collector-contrib/receiver/awscontainerinsightreceiver/internal/k8swindows/extractors   (cached)
ok      github.com/open-telemetry/opentelemetry-collector-contrib/receiver/awscontainerinsightreceiver/internal/k8swindows/hcsshim      (cached)
ok      github.com/open-telemetry/opentelemetry-collector-contrib/receiver/awscontainerinsightreceiver/internal/k8swindows/kubelet      (cached)

2. PR checks can confirm unit tests passing on Linux
3. Complete e2e testing passed.

4. Sample of output in performance log group for Windows node

{
    "AutoScalingGroupName": "eks-windows-2022-mng-42c6d6f1-7ce3-0ec3-XXXXXXXXXXXXXXX",
    "CloudWatchMetrics": [
        {
            "Namespace": "ContainerInsights",
            "Dimensions": [
                [
                    "ClusterName",
                    "InstanceId",
                    "NodeName"
                ],
                [
                    "ClusterName"
                ]
            ],
            "Metrics": [
                {
                    "Name": "node_status_condition_pid_pressure",
                    "Unit": "Count"
                },
                {
                    "Name": "node_status_condition_disk_pressure",
                    "Unit": "Count"
                },
                {
                    "Name": "node_status_condition_memory_pressure",
                    "Unit": "Count"
                },
                {
                    "Name": "node_cpu_reserved_capacity",
                    "Unit": "Percent"
                },
                {
                    "Name": "node_status_allocatable_pods",
                    "Unit": "Count"
                },
                {
                    "Name": "node_status_condition_ready",
                    "Unit": "Count"
                },
                {
                    "Name": "node_status_condition_unknown",
                    "Unit": "Count"
                },
                {
                    "Name": "node_number_of_running_pods",
                    "Unit": "Count"
                },
                {
                    "Name": "node_cpu_limit"
                },
                {
                    "Name": "node_status_capacity_pods",
                    "Unit": "Count"
                },
                {
                    "Name": "node_memory_limit",
                    "Unit": "Bytes"
                },
                {
                    "Name": "node_cpu_usage_total"
                },
                {
                    "Name": "node_memory_working_set",
                    "Unit": "Bytes"
                },
                {
                    "Name": "node_memory_reserved_capacity",
                    "Unit": "Percent"
                },
                {
                    "Name": "node_network_total_bytes",
                    "Unit": "Bytes/Second"
                },
                {
                    "Name": "node_cpu_utilization",
                    "Unit": "Percent"
                },
                {
                    "Name": "node_memory_utilization",
                    "Unit": "Percent"
                },
                {
                    "Name": "node_number_of_running_containers",
                    "Unit": "Count"
                }
            ]
        }
    ],
    "ClusterName": "XXXXX-CI-2022",
    "InstanceId": "i-XXXXXXXXXXXX",
    "InstanceType": "m5.large",
    "NodeName": "ip-XX-XX-XX-XX.us-west-2.compute.internal",
    "OperatingSystem": "windows",
    "Sources": [
        "kubelet",
        "pod",
        "calculated"
    ],
    "Timestamp": "1709726796214",
    "Type": "Node",
    "Version": "0",
    "kubernetes": {
        "host": "ip-XX-XX-XX-XX.us-west-2.compute.internal"
    },
    "node_cpu_request": 550,
    "node_cpu_usage_system": 0,
    "node_cpu_usage_user": 0,
    "node_memory_pgfault": 0,
    "node_memory_pgmajfault": 0,
    "node_memory_request": 448790528,
    "node_memory_rss": 0,
    "node_memory_usage": 2205806592,
    "node_network_rx_bytes": 324.75,
    "node_network_rx_dropped": 0,
    "node_network_rx_errors": 0,
    "node_network_tx_bytes": 207.86666666666667,
    "node_network_tx_dropped": 0,
    "node_network_tx_errors": 0,
    "node_cpu_limit": 2000,
    "node_cpu_reserved_capacity": 27.500000000000004,
    "node_cpu_usage_total": 2,
    "node_cpu_utilization": 0.1,
    "node_memory_limit": 8274866176,
    "node_memory_reserved_capacity": 5.423538199344531,
    "node_memory_utilization": 7.9183519112418335,
    "node_memory_working_set": 655233024,
    "node_network_total_bytes": 532.6166666666666,
    "node_number_of_running_containers": 2,
    "node_number_of_running_pods": 2,
    "node_status_allocatable_pods": 110,
    "node_status_capacity_pods": 110,
    "node_status_condition_disk_pressure": 0,
    "node_status_condition_memory_pressure": 0,
    "node_status_condition_pid_pressure": 0,
    "node_status_condition_ready": 1,
    "node_status_condition_unknown": 0
}

5. Link to Integ tests results for both Linux and Windows. CW agent runs successfully on Both Linux and Windows. Fluenbit fails due to timeout issue when destroying the cluster. There is no issue in functional working of fluentbit.
   https://github.com/aws/private-amazon-cloudwatch-agent-staging/actions/runs/8175470234/job/22352686273

Documentation:
This commit adds documentation - #166

[nathalapooja]

There are no tests for this file methods

[KlwntSingh]

I added tests for this file. Unit test coverage is only limited to initializing k8sWindows object.
Adding unit test for GetMetrics will require some refactoring. Can follow up with adding unit test ater release.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 44.32432% with 103 lines in your changes are missing coverage. Please review.

❗ No coverage uploaded for pull request base (aws-cwa-dev@9cb314e). Click here to learn what that means.

Files	Patch %	Lines
receiver/awscontainerinsightreceiver/receiver.go	11.11%	31 Missing and 1 partial ⚠️
internal/aws/k8s/k8sclient/clientset.go	16.66%	25 Missing ⚠️
...ainerinsightreceiver/internal/host/nodeCapacity.go	31.81%	14 Missing and 1 partial ⚠️
...eiver/internal/stores/kubeletutil/kubeletclient.go	0.00%	14 Missing ⚠️
internal/aws/containerinsight/utils.go	0.00%	7 Missing ⚠️
internal/kubelet/client.go	60.00%	3 Missing and 1 partial ⚠️
...ontainerinsightreceiver/internal/host/ebsvolume.go	50.00%	2 Missing and 1 partial ⚠️
...scontainerinsightreceiver/internal/stores/utils.go	91.89%	2 Missing and 1 partial ⚠️

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@              Coverage Diff               @@
##             aws-cwa-dev     #180   +/-   ##
==============================================
  Coverage               ?   82.44%           
==============================================
  Files                  ?     1772           
  Lines                  ?   165884           
  Branches               ?        0           
==============================================
  Hits                   ?   136767           
  Misses                 ?    25131           
  Partials               ?     3986           

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

[nathalapooja]

{
"Name": "node_cpu_limit"
},
and
{
"Name": "node_cpu_usage_total"
},
metrics are missing units. May I know why didn't we include the statsd and emf integ testing for windows EKS?Have you added additional unit tests from yesterday discussion for Extractor helpers class?

[KlwntSingh]

{ "Name": "node_cpu_limit" }, and { "Name": "node_cpu_usage_total" }, metrics are missing units. May I know why didn't we include the statsd and emf integ testing for windows EKS?Have you added additional unit tests from yesterday discussion for Extractor helpers class?

The following metrics are reported in unit of millicores, and cloudwatch doesn't support it.