Enable Worker Latency Profiles support non default wokrer MCPs

• Proposed title of this feature request

This is more a Feature extension rather than a new feature therefore i don't think this field is required to be set.

• What is the nature and description of the request?

At the moment the Machine Config Operator using Worker Latency Profiles  in the nodes.config CR is changing some parameters in some Red Hat Openshift Container Platform system components to make the lease renew of the nodes under the default worker Machine Config Pool less strict. One of these changes is the kubelet parameter nodeStatusUpdateFrequency on the node level that is getting set using a kubeletconfig.

The requested action is to extend this functionality so also nodes under custom Machine Config Pools to be able to get updated the kubelet configuration with the nodeStatusUpdateFrequency parameter. 

Having also a way to choose which MCPs will get configured would be also a plus but this is my idea. The customer only asked for support for custom MCPs as a basic requirement.

• Why does the customer need this? (List the business requirements here)

For big clusters with hundreds of nodes under cluster custom MCPS this will provide relief to the API.

This will provide relief on big clusters with low network Latency without the user to need to apply manually a kubeletconfig.

The customer need this for resolving some issues on a big cluster with nodes flapping from Ready to NotReady but we have not yet identified if the Worker Latency Profile will provide any relief as it is still under investigation. But i think that regardless the outcome will be this can still be a valid request for this feature.

• List any affected packages or components.

Machine Config Operator

Kubelet