See https://redhat-internal.slack.com/archives/CK1AE4ZCK/p1696528164774999 for additional context, but the featureGates in the kubelet.yaml templates here and here are hard-coded (and have been for awhile), and we really should be retrieving them from the featueGateAccessor and injecting them.

This will make sure that:

• They are always in sync
• They shouldn't be able to skew anymore when featureGates graduate or get removed

Which makes everything better for everyone.

We don't need to filter the FeatureGates for kubelet-only, because apparently OpenShift carries a patch that makes kube stuff accept and ignore FeatureGates they don't understand, so we'll at least be in good company with the apiserver and the controller manager who also do not filter their featureGates.

Done When:

• FeatureGates in kubelet.yaml template are no longer hard coded
• FeatureGates in kubelet.yaml are retrieved from the featureGateAccessor and injected into the template
• all tests pass