runAsUser SecurityContext not working for windows

[dloucasfx]

Based on kubernetes/kubernetes#102849 runAsUser is not currently working for windows.
This prevents the agent from starting

Events:
  Type     Reason             Age   From                     Message
  ----     ------             ----  ----                     -------
  Normal   Scheduled          16s   default-scheduler        Successfully assigned default/splunk-otel-collector-1685115615-agent-gsb8n to ip-10-10-7-216.ec2.internal
  Normal   ResourceAllocated  16s   vpc-resource-controller  Allocated Resource vpc.amazonaws.com/PrivateIPv4Address: 10.10.11.36/19 to the pod
  Warning  FailedMount        16s   kubelet                  MountVolume.SetUp failed for volume "kube-api-access-26vnh" : chown c:\var\lib\kubelet\pods\3905601f-f6c7-401a-a328-e44bf75d80a6\volumes\kubernetes.io~projected\kube-api-access-26vnh\..2023_05_26_15_40_20.3621507769\token: not supported by windows
  Warning  FailedMount        16s   kubelet                  MountVolume.SetUp failed for volume "kube-api-access-26vnh" : chown c:\var\lib\kubelet\pods\3905601f-f6c7-401a-a328-e44bf75d80a6\volumes\kubernetes.io~projected\kube-api-access-26vnh\..2023_05_26_15_40_20.1631205512\token: not supported by windows
  Warning  FailedMount        14s   kubelet                  MountVolume.SetUp failed for volume "kube-api-access-26vnh" : chown c:\var\lib\kubelet\pods\3905601f-f6c7-401a-a328-e44bf75d80a6\volumes\kubernetes.io~projected\kube-api-access-26vnh\..2023_05_26_15_40_22.3704774755\token: not supported by windows
  Warning  FailedMount        12s   kubelet                  MountVolume.SetUp failed for volume "kube-api-access-26vnh" : chown c:\var\lib\kubelet\pods\3905601f-f6c7-401a-a328-e44bf75d80a6\volumes\kubernetes.io~projected\kube-api-access-26vnh\..2023_05_26_15_40_24.1619713144\token: not supported by windows

This PR checks if runAsUser is defined in the securityContext for a windows agent, cluster-receiver and gateway and remove it if it exists.

Finally, I have noticed that revert-patch-log-dirs-hook.yaml is rendered for windows when securityContext.runAsUser and securityContext.runAsGroup are defined, although runAsUser does not work on windows, I aded an extra check to make sure not to bother when it's windows.

Note: I still need to do more validation and testing as we changed some requirements. Still need to recover Fluentd and use the helper in other places