feat(argocd): add permission support for argocd

[karthikjeeyar]

Fixes:

https://issues.redhat.com/browse/RHIDP-1796

Description:

This PR adds support for RBAC permission in argocd plugin. argocd.view.read Permission allows the user view the argocd plugin components in overview and CD tabs.

Screenshots:

Without argocd.view.read Permission:

With argocd.view.read Permission

---

How to test:

1. Configure the Argocd plugin and add Github integration.
2. Create a policy file rbac.csv for the permission policies

    g, user:default/<YOUR_USERNAME>, role:default/argocd-viewer
    
    p, role:default/argocd-viewer, argocd.view.read, read, allow
  

    p, role:default/argocd-viewer, catalog-entity.read, read, allow
    p, role:default/argocd-viewer, catalog-entity.create, create, allow

3. Configure the RBAC Backend plugin to include the argocd permission.

  enabled: true
  rbac:
    policies-csv-file: ../<PATH>/<TO>/<CSV>/rbac-policy.csv
    policyFileReload: true

4. Annotate the catalog component to include argocd application selector

    'argocd/app-selector': rht-gitops.com/janus-argocd=quarkus-app-bootstrap

5. Register the component and view the CD tab to see the argo applications working.
6. Now deny the argocd.view.read permission from the rbac.csv file and wait for the application to auto-reload. you should see the Permission required alert.

---

Unit tests:

 PASS  src/components/DeploymentSummary/__tests__/DeploymentSummary.test.tsx (6.254 s)
  DeploymentSummary
    ✓ should not render deployment summary table when the user does not have view permission (3 ms)

 PASS  src/components/DeploymentLifeCycle/__tests__/DeploymentLifecycle.test.tsx
  DeploymentLifecycle
    ✓ should render Permission alert if the user does not have view permission (91 ms)

cc: @kim-tsao @rohitkrai03 @nickboldt @invincibleJai

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign invinciblejai for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[karthikjeeyar]

@AndrienkoAleksandr @PatAKnight I see a semantic-relase-bot bumped the rbac-common plugin from 1.6.0 to 1.6.1
@janus-idp/backstage-plugin-rbac-common 1.6.1 here - 9bb8c47 but rbac plugin still references 1.6.0 here so there is a mismatch in yarn.lock file causing the above checks to fail ^^ . Let me know if I should bump the version in rbac plugin manually ?

[AndrienkoAleksandr]

+1 to bump manually