[Monitoring V2] windows-exporter should no longer depend on rancher/wins

[aiyengar2]

Currently, Monitoring V2 for Windows has a dependency on the underlying distribution using rancher/wins and supporting the ability to mount the established wins named pipes to execute host-process operations on the host.

https://github.com/rancher/charts/blob/8a4cd82fddc632d059d587a47aa7dd318e0781b7/charts/rancher-windows-exporter/100.0.0/templates/daemonset.yaml#L31-L49

This dependency should be removed to allow Monitoring V2 to be installed onto non-RKE2 clusters.

[github-actions]

This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions.

[HarrisonWAffel]

This issue can now be tested as the charts PR for 2.8 has been merged. Version 103.1.0-rc1+up45.31.1 should be used to test this issue. Basic functionality testing for monitoring windows nodes as well as chart upgrade and downgrade paths should be tested.

Testing of the related changes for 2.9 will be tracked in #234

[slickwarren]

did some testing; currently blocked due to an issue with exporter not liking the fact that wins is on an RC'd version. Harrison is aware of this issue and will push a fix once the proxy testing is done

[HarrisonWAffel]

rancher-wins has been bumped in v2.8, this is no longer blocked

[slickwarren]

tested on v2.8-head (421ce19)

• deploy a windows cluster on 1.27 using the currently released chart
  • upgrade the chart to 103.1.0-rc1+up45.31.1 -- pass
• deploy a windows cluster on the latest k8s version available (1.28)
  • install the chart 103.1.0-rc1+up45.31.1 -- pass