Native ARM64 CI builds and tests

[Avasam]

Announcement: https://github.com/orgs/community/discussions/155713

Predecessor / based on:

• [Merge by June 2025] Update to Windows 2022 runner image #2582
• Shorten --config-setting=--build-option commands #2583
• Add Python 3.9 ARM64 wheel #2584
• Remove actions/setup-python#1005 workaround #2645

Changes unique to this PR:

• Updated artefacts names
• Add ARM64 to the Build and test job
• Keep cross-compiling before Python 3.11
• Updated link in make_all.bat to directly point to cross-compilation info

[Avasam]

Alright, I'm getting actual failed tests on ARM64 now. Not too surprising since I doubt many contributors have an AMR64 Windows machine.

I think this is the failing test: https://github.com/mhammond/pywin32/actions/runs/14699426077/job/41246179979?pr=2581#step:11:500

Traceback (most recent call last):
  File "C:\a\pywin32\pywin32\com\win32com\test\testPyComTest.py", line 53, in <module>
    universal.RegisterInterfaces("{6BCDCB60-5605-11D0-AE5F-CADD4C000000}", 0, 1, 1)
  File "C:\Users\runneradmin\AppData\Roaming\Python\Python311-arm64\site-packages\win32com\universal.py", line 76, in RegisterInterfaces
    _doCreateVTable(iid, name, is_dispatch, method_defs)
  File "C:\Users\runneradmin\AppData\Roaming\Python\Python311-arm64\site-packages\win32com\universal.py", line 86, in _doCreateVTable
    vtbl = pythoncom._univgw.CreateVTable(defn, is_dispatch)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
testit (__main__.PyCOMTest.testit) ... FAIL
NotImplementedError: not implemented on this platform

The only matching error message I could find is this:

pywin32/com/win32com/src/univgw.cpp

Lines 264 to 268 in ddc14b2

	#else // other arches
	/* The MAINWIN toolkit allows us to build this on Linux!!! */
	#pragma message("XXXXXXXXX - win32com.universal won't work on this platform - need make_method")
	PyErr_SetString(PyExc_NotImplementedError, "not implemented on this platform");
	code = NULL;

[Avasam]

I carved this very specific exception so that if support is added (or attempted) and the error changes or disappears, this will have to be updated accordingly (hopefully by removing the try-except entirely)