Add Linux tolerations for all deployments

[nickgerace]

With a "Windows cluster", there may not actually be any Windows node in a "Ready" state yet. In case pods have to fall back to Linux nodes, they need to toleration to do so.

Discovered by @sowmyav27

[sowmyav27]

I have a windows cluster, but no windows nodes yet. Have 1 etcd+control and 3 worker nodes linux nodes. No windows nodes.
I see fleet is unscheduled state. (on 2.5-head - commit id: 2f2cfe63)

0/4 nodes are available: 1 node(s) had taint {node-role.kubernetes.io/controlplane: true}, that the pod didn't tolerate, 3 node(s) had taint {cattle.io/os: linux}, that the pod didn't tolerate.

Expected:
Fleet should be deployed successfully

[nickgerace]

#323 has been merged, but we should get a newly tagged chart into rancher/charts

[nickgerace]

A new chart has been tagged: v0.3.5-rc2

[thehejik]

Successfully validated the fix.

HA upstream cluster based on rancher:v2.5-head 93d921f with rancher/fleet:v0.3.5-rc2 automatically deployed from dev-v2.5 helm chart repo.

After bootstraping a downstream windows cluster (flannel,VXLAN), with 3 linux nodes only (same roles - etcd, control, worker), I see there is one Running/Active replica of fleet-agent pod using rancher/fleet-agent:v0.3.5-rc2 image.

---

The issue is reproducible on rancher:2.5.7 with rancher/fleet:v0.3.4 - the fleet-agent pod on downstream windows cluster (only linux nodes) is not running and failing on:

[Unschedulable] 0/3 nodes are available: 3 node(s) had taint {cattle.io/os: linux}, that the pod didn't tolerate.

[sowmyav27]

Reopening for a check on master-head in dev-v2.6 feature charts branch

[thehejik]

Blocked by broken Cluster Explorer in master-head 077fbf6- fleet-agent pod is not deployed when looking over kubectl/ember.

[sowmyav27]

Blocked because of this issue - rancher/rancher#31964

[thehejik]

Closing this, tracking master-head validation here - #339