Feature: RBAC for FluxCD and ArgoCD applications

[pawan-59]

🔖 Feature description

Argo CD and Flux CD app listings in Devtron are gated behind super-admin. Any user who needs to see or debug a GitOps application — including the developer who owns it — must either be made a super-admin or keep using a separate Argo CD / Flux dashboard. Both outcomes are bad: the first is a security and compliance objection we hit in enterprise evaluations, the second defeats the single-pane-of-glass value proposition that the Argo/Flux listing was built for.

Product doc: https://docs.google.com/document/d/1bNzgZoJzLAaCGeCLPgykMaexZI1if4a1tmpznp332QI/edit?usp=sharing
Tech doc: https://docs.google.com/document/d/15Jxp-_RiGO2tyK-T_GBt6V4A_f-DrUpuEQ30DkHg6iE/edit?usp=sharing

🎤 Pitch / Usecases

Right now only super admin users are able to view FluxCD application on Devtron UI. But not the other users

🔄️ Alternative

No response

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

✅ Action items

BE tasks

• Setting up a dev environment with external argo/flux apps within different namespaces and multiple clusters so that development scenarios can be tested
• Load policies - migrations
• Add to orchestrator/user/check/role - send flags to tell if the user can view argo/flux tabs
• Drop down changes - /orchestrator/user/resource/options/{kind}/{version}
• Apply enforcements
• Testing

FE tasks

• Show argo/flux tabs based on response sent from the backend
• Add support for new access type in the role filter while creating/updating permissions
• New kind in /orchestrator/user/resource/options/{kind}/{version}
• Testing