refactor: remove argo workflows

[gabor-boros]

Description

Remove the Argo Workflows UI and configures RBAC for argoCD only.

Testing

1. Remove the resources manually with kubectl that are removed by this PR
2. In an existing cluster, run the install command

SE-6524

[kaustavb12]

LGTM 👍

Just added a couple of clarifications.

• I tested this: Tested in a cluster
• I read through the code
• I checked for accessibility issues
• Includes documentation
• Added to the Code Drift project board (for backports)

[kaustavb12]

@gabor-boros I am not very familiar with ApplicationSet, so just wanted to flag this for verification from your end that write access to application set is appropriate for developer role. I say this because this doc mentions:

ApplicationSet controller may also be used to allow developers (without access to the Argo CD namespace) to independently create Applications without cluster-administrator intervention.

This sort of implies to me that application sets are something an admin is meant to create which can then be used by developers to create applications.

[kaustavb12]

@gabor-boros I am not sure we want to give developers write access to projects. I am thinking in the context of the axim cluster, where we plan to create a "superuser" for that project.

Here, the developer role as configured now, seems the most appropriate "superuser" role since I don't want this "superuser" to have access to things like gpg keys, certificates, etc. I am wondering if write access projects is required here at all or should it be reserved for the actual "cluster admin" role.