[v0.12] Fleet job pods do not receive tolerations from values.yaml

[weyfonk]

Forward-port of #3180 to v0.12.

[weyfonk]

Additional QA

Problem

Installing Fleet charts in a cluster where all nodes are tainted would fail, because Fleet jobs did not support node tolerations coming from chart values. This would result in Fleet failing to install.
Affected jobs were the cleanup jobs for cluster registrations and completed jobs.

Solution

The Fleet chart now propagates node tolerations from chart values to those jobs, as it does for other deployed pods.

Testing

Engineering Testing

Manual Testing

This has been tested by tainting one node in a k3d cluster, and checking that:

• deployment was successful
• jobs were not scheduled on the tainted node, unless the corresponding toleration was set in chart values

Automated Testing

N/A

QA Testing Considerations

It would make sense to test this in a cluster where all nodes are tainted:
* if no tolerations are specified in chart values, running the above mentioned jobs should still fail
* setting tolerations matching at least one node's taints should enable successful deployment, with both jobs being created and run successfully.

This can be tested as follows:

1. Add tolerations to a separate values file, eg. values.yaml
2. Ensure that helm repo list lists https://rancher.github.io/fleet-helm-charts/; if not, add it.
3. Refresh Helm repositories with helm repo update
4. Check the Fleet Helm repo for its latest available version, e.g. helm search repo fleet-repo --devel
5. Use that latest version to template a Fleet chart installation with helm template fleet fleet-repo/fleet --version=$latest_version (where $latest_version is the version found in the previous step), checking that no extra tolerations are applied to jobs fleet-cleanup-clusterregistrations and job_cleanup_gitrepojobs.yaml
6. Repeat the previous step with flag -f values.yaml and check that tolerations set in that file are applied to both jobs

Regressions Considerations

N/A