Feature Overview (aka. Goal Summary)

Roadie Scaffolder ArgoCD plugin is not compatible with our ArgoCD backend plugin because it has Roadie ArgoCD backend plugin as a dependency. 

To support Scaffolder actions for Community ArgoCD, two approaches can be taken. Either create a new Community ArgoCD backend module for ArgoCD resource creation, or extract shared ArgoCD API into Roadie `argocd-common` plugin, which then can be used by Roadie Scaffolder ArgoCD plugin, removing its current backend dependency.

Goals (aka. expected user outcomes)

Community ArgoCD plugin has been created to correctly implement permissions for ArgoCD and to display them in RBAC UI (RHTAPUI-12). Customers experience confusion due to the presence of multiple ArgoCD plugins, and require a clear, unified experience. Therefore, this feature aims to ensure our Community ArgoCD plugin provides 
functionality equivalent to the existing Roadie plugin, including integration with ArgoCD Scaffolder actions.

Requirements (aka. Acceptance Criteria):

• Users will be able to create ArgoCD resources with scaffolder actions when Community ArgoCD plugin is enabled.
• ArgoCD permissions will maintain working correctly.

Documentation Considerations

• As a platform engineer, I want to be able to find information on how to configure ArgoCD Scaffolder actions when Community ArgoCD plugin is enabled

ArgoCD plugin is community supported, so no official documentation is required for this feature.