Python: fix limited API logic under GCC on Windows

[amcn]

When building a limited API module on Windows with GCC the library to link with should be python3.dll, not python3X.dll.

[eli-schwartz]

When building a limited API module on Windows with
GCC the library to link with should be python3.dll,
not python3X.dll.

Maybe:

When building a limited API module on Windows the library
to link with should be python3.dll, not python3X.dll. This was
already the case for non-GCC, but should have been the case
unconditionally.

[amcn]

Fingers crossed this fixes the issue that both @sdimovv and @lpsinger have encountered during the discussion of #13171.

Feedback very welcome.

[amcn]

Updated commit message as suggested. The fix is much clearer now in the log.

[astro-stan]

Thanks for the quick fix!

Is there an easy way to test this before the next RC? Preferably on GH actions, as I don't have easy access to a Windows machine.

[eli-schwartz]

pip install git+https://github.com/amcn/meson@python-gcc-win32-limited-api

(somewhere in the "before" actions for cibuildwheel, I presume.)

[lpsinger]

That did the trick. It's working for me:

https://github.com/nasa-gcn/hpx/actions/runs/9768042891/job/26964677305?pr=21

Thanks!

[astro-stan]

Worked for me too!

Thanks!

[eli-schwartz]

Just rerunning CI with a commit to get the cygwin runner passing.