Feature Overview (aka. Goal Summary)

Today, there are a number of plugins that have implemented permissions that are unable to be viewed from within the RBAC UI. This is because they are either missing the permission declaration through the use of passing them to the `createPermissionIntegrationRouter` in their respective backend or they do not have a backend plugin at all. These plugins include: Topology, Tekton, Quay, and Red Hat ArgoCD.

Goals (aka. expected user outcomes)

To see Topology permissions in RBAC UI so that users can create roles with Topology permissions.

Requirements (aka. Acceptance Criteria):

• Remove custom Topology permissions, remove now not needed `@backstage-community/plugin-topology-common`
• Use Kubernetes permissions kubernetes.clusters.read and kubernetes.resources.read for topology plugin instead of custom @backstage-community/plugin-topology-common topology.view.read permission.
• Update topology permission alert for missing kubernetes.clusters.read and kubernetes.resources.read permissions.
• Add topology permission alert for missing kubernetes.proxy permission when accessing pod logs.
• Update RBAC documentation regarding Topology permissions.