Removed componentstatuses permission due to deprecation

[valipashask26]

Deprecation of componentstatuses API and Removal from ClusterRole

The ``componentstatuses``` API has been deprecated since Kubernetes v1.19+, causing frequent warnings and generating excessive log noise for customers on the latest versions.

To address this issue, we have removed componentstatuses from the ClusterRole YAML (001_kube_enforcer_config.yaml).

Upon reviewing the code, this API was only used to check the health status of core control plane components like kube-scheduler, kube-controller-manager, and etcd. The implementation simply verifies the required permissions, and if missing, logs a warning. However, in AKS clusters, customers have been repeatedly receiving deprecated API call warnings in their cluster logs.

Reference:

Support Case: #48261 Screenshot:

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

sk Valipasha seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[seanposner]

Will be addressed on a global level.