Currently if a user tries to edit the machine configuration (and PIDs limit) of a cluster that he doesn't own, when trying to save he'll get a "403 Forbidden access to create resource".

We should do better and disable the "Edit machine configuration" button if the user doesn't have the rights to edit the configuration.

It's possible to check the users permissions related to the machine configuration by calling "api/authorizations/v1/self_resource_review" and passing "ClusterKubeletConfig" as resource type. See this MR for more details.

Acceptance criteria

• Fetch the rights related to the kubelet config
• Disable the Edit machine configuration button if the write permission is absent