Upon helm upgrade with new config, retina-win daemon Seet does not cause pod rollout

[vpidatala94]

Describe the bug
If a customer attempts to perform a helm upgrade to enable pod level metrics and annotations. What is being seen is that the retina win pods do not get recreated by daemon set unlike Linux with the impact being the config changes get applied

This is despite that both Linux and Windows retina-win config maps picks the new changes.

Expected behavior
Pod re-creates/rollout event initiated by retina-win daemon set allowing the new retina-win config changes to get applied so that the plugins can work accordingly.

• OS: Windows