CI: Test Github Actions Arm64 Runners

[lithomas1]

• closes #xxxx (Replace xxxx with the GitHub issue number)
• Tests added and passed if fixing a bug or adding a new feature
• All code checks passed.
• Added type annotations to new arguments/methods/functions.
• Added an entry in the latest doc/source/whatsnew/vX.X.X.rst file if fixing a bug or adding a new feature.

[lithomas1]

Looks like we're too early :(

some issues with micromamba it seems.

[mroeschke]

I think the job name: and concurrency group: will need to account for matrix.platform now

[mroeschke]

some issues with micromamba it seems.

Might be worth raising an issue in https://github.com/mamba-org/setup-micromamba/?

[lithomas1]

issue could be actions/partner-runner-images#25?

[lithomas1]

This should be mostly working (failures don't seem like my fault?)

[mroeschke]

Thanks @lithomas1. We're on our way to removing the CircleCI builds!

[lithomas1]

@meeseeksdev backport 2.3.x

[lumberbot-app]

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout 2.3.x
git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 b98336653128790661d4c66d398f3e44d481dd3b

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #60722: CI: Test Github Actions Arm64 Runners'

4. Push to a named branch:

git push YOURFORK 2.3.x:auto-backport-of-pr-60722-on-2.3.x

5. Create a PR against branch 2.3.x, I would have named this PR:

"Backport PR #60722 on branch 2.3.x (CI: Test Github Actions Arm64 Runners)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.

[lithomas1]

Let's backport this - I think I was having issues with build versioning last release on the Circle jobs.

Consolidating under GHA should provide better observability/debugability into failures in general.

[jorisvandenbossche]

Only backporting the wheel change could be sufficient then?

[lithomas1]

Only backporting the wheel change could be sufficient then?

Yes, but the GHA jobs have better coverage so we might as well backport that too.

[jorisvandenbossche]

Manual backport -> #60780