ci: build and test Windows ARM64 wheels (CPython 3.11-3.14t)

[johnnynunez]

Adds a native windows-11-arm entry to the cibuildwheel matrix in wheels.yml, so releases also ship Windows on Arm wheels. Each wheel is tested with the existing pytest suite, the same as on the other platforms.

• Builds and tests CPython 3.11, 3.12, 3.13, 3.14 and 3.14t (win_arm64).
• Skips cp39 and cp310 on that runner. The extension builds for them, but NumPy (needed by the tests) publishes no win_arm64 wheels for those versions, so pip falls back to a source build of NumPy, which fails (failed attempt).
• The other Windows entry keeps the previous auto architectures (AMD64 + x86). Linux and macOS are unchanged.

Verification on my fork, same cibuildwheel settings on the current master source (publishing step removed): https://github.com/johnnynunez/daqp/actions/runs/38318252436. All five wheels built and passed the suite (39 passed each). Every .pyd is a native ARM64 PE (machine 0xAA64). On 3.14t the only warning is the usual one that the module hasn't declared free-threading support, so the GIL is enabled on import.

[darnstrom]

Thank you for contributing @johnnynunez. Is there a reason why this is limited to CPython 3.12? I'd expect 3.11, 3.13, and 3.14 to work on windows 11-arm too.

[johnnynunez]

Thanks @darnstrom, no good reason: it was too narrow. I've updated the PR so the windows-11-arm entry builds and tests CPython 3.11, 3.12, 3.13, 3.14 and 3.14t. On my fork all five wheels built and passed the test suite (39 passed each): https://github.com/johnnynunez/daqp/actions/runs/38318252436

cp39 and cp310 are skipped on that runner only because NumPy, which the tests use, has no win_arm64 wheels for them. The extension itself builds fine for those versions. If you'd rather ship them untested, I can switch those two to CIBW_TEST_SKIP instead.

(Edit: an earlier version of this comment also excluded 3.14t; NumPy does ship 3.14t win_arm64 wheels, so it's now included.)