Feat: Protected Principals for ACLs via RBAC

[RotemCDos]

• Breaking change? (if so, please describe the impact and migration path for existing application instances)

Currently, when working in an admin-client environment type, the client is able to edit all or none of the ACLs.
This might cause an issue where the client will remove the Kafbat UI ACLs and softlock themselves until the cluster admin inserts them back via code.

What changes did you make? (Give an overview)
These changes were inspired by #288 with less capabilites, however I still believe this is enough.
Added an option for protectedPrincipals (non wildcard) under a specific role in the RBAC file. Any ACL binding whose principal matches one of these strings will be blocked from modification by that role.

Is there anything you'd like reviewers to focus on?

How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

• No need to
• Manually (please, describe, if necessary)
• Unit checks
• Integration checks
• Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
• My changes generate no new warnings (e.g. Sonar is happy)
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged

Check out Contributing and Code of Conduct

A picture of a cute animal (not mandatory but encouraged)