feat: Support for multiple rbac ConfigMaps (Alpha)

[meln5674]

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• The title of the PR conforms to the Toolchain Guide
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).
• My new feature complies with the feature status guidelines.
• I have added a brief description of why this PR is necessary and/or what this PR solves.
• Optional. My organization is added to USERS.md.
• Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

Fixes #8324

This work is based on these abandoned PRs:

• feat: additional RBAC configmaps #9976
• feat: ability to add additional configmaps #11445

In large multi-tenant instances, the size of the policy.csv may exceed the limit for a single Kubernetes resource.

This patch adds the label argocd.argoproj.io/cm-type=policy-csv, which, when placed on a configmap in the same namespace, causes it to be included in the casbin policy according to the same rules as the existing argocd-cm-rbac configmap, with outputs sorted alphabetically by configmap name before concatenation to ensure predictable outputs.

The admin CLI has been updated to also check for these additional configmaps and generate the final policy accordingly.

E2E tests have been added to ensure that these extra configmaps' policies are included when created, as well as correctly removed when they are changed or updated.

NOTE: I could have sworn I made this PR as a draft a few days ago, but it was gone when I went to update it. Please excuse me if I've accidentally made a duplicate