Fix windows 3.13 wheels again

[ddelange]

it seems we have CI rot coming from external/upstream changes somewhere in the past two weeks: just tried releasing 1.0.1 fc75159...4f172e2 and we're no longer green

[ddelange]

something broke upstream in the past two weeks.

this is now necessary to get python313.lib discovered by maturin.

without this, we again hit PyO3/maturin-action#292:

fatal error LNK1181: cannot open input file 'python313.lib'

we encountered and fixed in #47 using generate-import-lib

now it manages to pass the 3.13 build again, but 3.13t is still red with LNK1181: ce73691 in this PR

both 3.13 and 3.13t were still working 2 weeks ago with all the same versions (maturin version, maturin-action version, pyo3 version, python 3.13.1 patch version): fc75159...4f172e2

tried both windows-2022 (no setup-python cache hit) and windows-2025 (python 3.13.1 cache hit), no difference.

[ddelange]

alright, we're green with 3.13t 🎉

turns out we don't need this Add python lib to PATH step. we need an explicit 3.13t distribution installed instead.

[oconnor663]

Haven't looked carefully yet but Merry Christmas all :)

[ddelange]

ok, windows 3.13t is green again 🎉 and now without generate-import-lib pyo3 extension enabled!

we're now simply setup-python'ing (near instant if py version is cached in the runner image) all python versions, including 3.13t, that we want to link against.

I wonder if 3.13t was really working 2 weeks ago...

now we'be become robust to external changes that github is making to the runner images.

[ddelange]

@oconnor663 lets make a squash&merge to avoid all these debug commits on master?

or even enable Require linear history in the branch protection of master?

I deleted the broken 1.0.1 Github Release and the git tag by running git push --delete origin 1.0.1, so we can squash and release a fresh 1.0.1