[r/r deployer] Support user-provide extraTolerations for SCC Operator

[mallardduck]

Issue

Rancher users should be able to provide their environment specific tolerations that are needed for Rancher and Rancher components. Because Rancher deploys the SCC Operator we need a way to control the way Rancher deploys the Operator via the Rancher Helm chart install process.

This is a SCC local version of: rancher/rancher#48541

---

Suggested Path

The SCC Deployer component lives inside of Rancher here: https://github.com/rancher/rancher/tree/main/pkg/scc/deployer

While the SCC Deployer is not a chart nor does it use the System Charts mechanism it does function in a similar way. As such our solution for the SCC and SCC deployer should mimic or directly "piggy-back" off the existing System Chart mechanism. The SCC Deployer will still be the component setting things up, however it should augment the deployment specs the same way a System Chart might.

In other words we should do something like:

• Add a SCC Operator key to: https://github.com/rancher/rancher/blob/main/chart/templates/configMap.yaml ,
• And add examples to values.yaml for rancher-prime repo,
• Modify the SCC Deployer to read from the ConfigMap (potentially needs a watcher that can re-trigger deploy if values change, but unsure)
• Review how other components use the priorityClassName field and consider following their examples that too.