Can't specify nodeSelector for SolrCloud / ZK / Busybox

**Problem**

If you have a multi platform node cluster (linux + windows) then you need to specify a `nodeSelector` to force a deployment to run on a specific node. Usually like this:
```
nodeSelector:
kubernetes.io/os: linux
```

If you don't have this setting in place then K8s will place them on a node as K8s seems fit. When this node turns out to be a Windows node the images needed for SolrCloud will not be able to be pulled, with a generic `ErrImagePull` in the events for the pods.

Trying to set `nodeSelector` in the `values.yaml` doesn't work for the SolrCloud installation. There are no errors, it just seems to be ignored.

**Solution**

Make SolrCloud use `nodeSelector` settings if they are set, preferrably in `values.yaml`, where any image is used (solr, zookeeper, busybox).

Start with values.yaml and the chart templates used by the SolrCloud installation, tracing deployments for Solr, ZooKeeper, and Busybox. Confirm how nodeSelector values are currently handled and verify that a configured selector reaches each workload. Done means the setting is honored for all three images without affecting installations that leave it unset.

Written by the indexing model from the issue text.