Description

This PR allows changes to the .Spec.Namespaces of TeamRoleBinding. Namespaces can be changed, but the webhook denies changing the TRB from cluster-scoped to namespace-scoped (by changing initially empty Namespaces) and vice versa (by removing all namespaces).
Changes to the Namespaces of TRB are reconciled by the TeamRoleBindingController. The removal of RoleBindings from the remote cluster changed to not only relying on .Spec.Namespaces, but to take into account the RoleBindings that could've been deployed before the change (now checked by the name of RoleBindings deployed).

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation Update
• 🎨 Style
• 🧑‍💻 Code Refactor
• 🔥 Performance Improvements
• ✅ Test
• 🤖 Build
• 🔁 CI
• 📦 Chore (Release)
• ⏩ Revert

Related Tickets & Documents

• Related Issue [FEAT] - Additional validation of TeamRoleBindings #765
• Closes [FEAT] - Allow changing Namespaces for TeamRoleBindings #764

Added tests?

• 👍 yes
• 🙅 no, because they aren't needed
• 🙋 no, because I need help
• Separate ticket for tests # (issue/pr)

I've added tests for the TeamRoleBinding controller and the TeamRoleBinding webhook.

Added to documentation?

• 📜 README.md
• 🤝 Documentation pages updated
• 🙅 no documentation needed
• (if applicable) generated OpenAPI docs for CRD changes

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• New and existing unit tests pass locally with my changes