Story

As a user of RHDH, I want to be able to create permissions for the Quay plugin through the use of the RBAC UI so that users can have limited access to the Quay plugin.

Background

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

The Quay plugin does not have a backend plugin of its own. We can look to migrate all of the Quay API calls from the frontend plugin to its own dedicated backend plugin. We could then use the `createPermissionIntegrationRouter` and pass the Quay permission to secure the routes.

Dependencies and Blockers

Another team owns the Quay plugins.

QE impacted work

Documentation impacted work

Acceptance Criteria

upstream documentation updates (design docs, release notes etc)

Technical enablement / Demo