[BUG] Mixed OS cluster - using NoSchedule taints affects Windows Nodes Exporter Daemonset

**Describe the bug**
By setting a noschedule taint at Windows node pools with `-taints node.kubernetes.io/os=Windows:NoSchedule` no metrics from Windows nodes are available because the node exporter DaemonSet doesn't get deployed.

**To Reproduce**
Create a node pool with `-taints node.kubernetes.io/os=Windows:NoSchedule` like described here: [mixed-OS Kubernetes clusters using node selectors or taints and tolerations](https://learn.microsoft.com/en-us/azure-stack/aks-hci/adapt-apps-mixed-os-clusters)
and check the monitoring data as described here:
[Monitor and logging data on Azure Kubernetes Service on Azure Stack HCI and Windows Server](https://learn.microsoft.com/en-us/azure-stack/aks-hci/monitor-logging)

**Expected behavior**
The Windows node exporter should tolerate noschedule taints.

**Screenshots**
A cluster without noschedule taints:

A cluster with noschedule taints at Windows nodepools

**Environment (please complete the following information):**
- AKS-HCI Version August 2022
- Kubernetes Version 1.23.5

**Additional context**

**Collect log files**

Locate the Windows node exporter DaemonSet configuration and inspect its scheduling rules against the reported Windows NoSchedule taint. Reproduce with a tainted Windows node pool, then verify that the exporter is deployed and Windows-node metrics are available while the taint remains.

Written by the indexing model from the issue text.