Dynamic Permissions Handling

[finally-fancy]

Description Busula should remove its navigation entirely as previously proposed in this document and rely on OpenMFP's navigation system which can dynamically manage permissions through Kubernetes RBAC. This would ensure that users only see resources they are authorized to view or edit. Additionally, Busula's content area should dynamically adjust based on user permissions, showing clear visual indicators (such as disabled buttons or read-only labels) when a user does not have write access to a resource. This solution provides a more secure, streamlined, and user-friendly experience without unnecessary clutter or errors.

Reasons In Busula's current implementation, the navigation system shows all available CRD objects in the UI regardless of whether the current user has the permissions to view or interact with them. This leads to a poor user experience because a user can see CRD entries in the navigation even if they lack the necessary permissions. When the user clicks on a CRD that they are not authorized to access, the system only displays an error message after the fact, causing frustration and unnecessary navigation.

Additionally, when a user has read-only permissions for a resource but no write access, there is no clear visual feedback to indicate that the resource is read-only. This makes it difficult for users to understand what actions they are allowed to perform and increases the risk of confusion during interactions.