Include unit/integration tests for Linux/ARM64 in GitHub Actions CI

# Summary

Hi Team,

I am working with ARGO-CD on the Linux/ARM64 platform.

ARGO-CD already releases **Linux/ARM64 binaries and the docker images**. However, there are [unit tests](https://github.com/argoproj/argo-cd/blob/master/.github/workflows/ci-build.yaml#L74) and [end-to-end](https://github.com/argoproj/argo-cd/blob/master/.github/workflows/ci-build.yaml#L340) tests running via GitHub Actions for Linux/AMD64 via [ci-build.yaml file](https://github.com/argoproj/argo-cd/blob/master/.github/workflows/ci-build.yaml). It would be great if these tests were also available for Linux/ARM64 via GitHub Actions CI.

I have tried running these tests for Linux/ARM64 using self-hosted ARM64 GitHub runners in my forked repo, but the tests are failing.

Unit tests are failing for bad credentials, as below:
~~~
error listing repositories for argoproj: GET https://api.github.com/orgs/argoproj/repos?per_page=100: 401 Bad credentials []
~~~
The failure logs are same for Linux/AMD64 in my forked repo’s GA job.

e2e tests are also failing for Linux/ARM64, to start k3s service on runners. However, tests are failing for my forked repo’s Linux/AMD64 jobs with the logs below:
~~~
Error: applicationset_test.go:402: Waiting 30 seconds to give the cluster a chance to delete the pods.
~~~

May I know, do you have plans to include integration tests for Linux/ARM64 in the GitHub Actions CI?

Kindly share your opinion on the same.

Start with .github/workflows/ci-build.yaml, especially the unit-test section around line 74 and the end-to-end section around line 340. Reproduce the reported Linux/ARM64 failures, including the GitHub API credentials error and the k3s-related failure at applicationset_test.go:402. Done means the relevant unit and end-to-end tests run successfully for Linux/ARM64 in GitHub Actions.

Written by the indexing model from the issue text.