CI: Build Linux AArch64 wheels natively, and add Arm runners for testing

[agriyakhetarpal]

Description

This PR switches the Linux arm64/aarch64 wheels to build natively on ubuntu-22.04-arm instead of using emulation.

(Hopefully?) fixes #787

Additional context

• https://github.blog/changelog/2025-01-16-linux-arm64-hosted-runners-now-available-for-free-in-public-repositories-public-preview/

[agriyakhetarpal]

For some reason, I can't trigger https://github.com/PyWavelets/pywt/actions/workflows/wheel_tests_and_release.yml. I do remember that those with triage permissions were able to do that at some point in the past, perhaps GitHub changed that... could you please trigger the workflow, @rgommers?

[agriyakhetarpal]

In the meantime, now that the runners are available, I can also expand the changes to tests.yml.

[agriyakhetarpal]

Perhaps I spoke too soon 😄 as the Linux job has vanished despite having perfectly fine syntax (I tried both ubuntu-22.04-arm both with and without the double quotes):

[rgommers]

Thanks! Switching to native runners looks like a good idea. The change in the wheels job looks right. The changes in tests.yml don't quite look right (aside from the possible syntax issue & disappearing job), because we don't want to double the number of jobs. Instead, can you please change 1 job over and leave the rest unchanged?

[agriyakhetarpal]

Thanks, @rgommers! I fixed the disappearing jobs; the error message was a bit cryptic.

because we don't want to double the number of jobs. Instead, can you please change 1 job over and leave the rest unchanged?

With 3a1ffa8, we're running only the "default" set of tests for Linux arm64, while Linux amd64 will run the "with-scipy", "minimum-req", "refguide-check", and "pre-releases" jobs in addition to the "default" set. Is this what you had in mind?

[rgommers]

Is this what you had in mind?

Closer, but not quite. On this PR I now see these 6 jobs:

That's pretty wasteful, there is no need for iterating over all Python versions already, let alone twice. I'd be fine with either 2 or 3 jobs there: we need to cover minimum/maximum Python version, and amd64/aarch64. So two jobs in total would cover that.

While you're at it, perhaps bump the maximum from 3.12 to 3.13?

[agriyakhetarpal]

Done; we now have two jobs with Python 3.10 and Python 3.13 for Linux amd64 (plus the extra jobs with options), and one job with Python 3.13 for Linux arm64.

[agriyakhetarpal]

0832609 does the same for macOS, bumping to Python 3.13. I notice we're not testing Intel macOS runners. Should we add them, or leave them out?

[agriyakhetarpal]

The segfault is unrelated and tracked via #782 already.

[rgommers]

LGTM now, let's give this a go (wheels get built on merge to main). Thanks Agriya!