feat: Implement Kubernetes Native RBAC Aggregation for cloud-manager

[stekik]

Description
This PR adds three aggregated ClusterRoles that automatically extend the standard Kubernetes view, edit, and admin roles with permissions for all cloud-manager CRDs

Changes proposed in this pull request:

Related issue(s)

[hyperspace-insights]

Control Panel

Hi, I'm an AI-powered Review Bot that helps you with summarizing and reviewing pull requests.
To interact with me, just use the following actions:

• 📝 Summarize PR
• 🔍 Agentic Review
• 🗑️ Delete all bot comments and reviews

---

💌 Have ideas or want to contribute? Create an issue and share your thoughts with us!
📑 Check out the documentation for more information.
📬 Subscribe to the Hyperspace PR Bot DL to get the latest announcements and pilot features!

Made with ❤️ by Hyperspace.

[dushanpantic]

We have both resource groups (cloud-control, cloud-resources) in same manifest which is not a possible scenario.

[dushanpantic]

Cloud manager aggregated roles should be installed to SKR when cloud-manager is enabled

[stekik]

Need clarification on:

• Should these be Roles (namespace-scoped) instead?
• Conditional deployment logic?

[tmilos77]

Do not change kustomization.yaml files
Create just one admin role for group cloud-resources.kyma-project.io and * resoucrea and verbs
Note that work doesn't end here, that also has to be added to the module manifest, check with @ijovovic and the release procecure

[dushanpantic]

cloud-control.kyma-project.io resources should not be part of these roles

[stekik]

@ijovovic The aggregated RBAC roles are now deployed to SKR via the installer (common directory pattern). Could you advise on the module manifest integration needed for the release procedure? cc @tmilos77