Update release workflow for Python 3.14

[ngoldbaum]

See ngoldbaum#9 where I hacked this together on my fork to test.

See https://github.com/ngoldbaum/tokenizers/actions/runs/22193203602/job/64186704987?pr=9 for the python-release workflow. I verified that all workflows are generating an abi3 and cp314t wheel.

maturin doesn't support Python 3.9 or pypy 3.9 and pypy 3.10 anymore. They do support pypy3.11, so I could add those builds if you want.

Pypy is not actively developed anymore, so from my perspective it doesn't make sense to start shipping pypy3.11 wheels only to need to stop shipping them next year when maturin drops support for pypy entirely.

[ArthurZucker]

Okay, as I am not too familiar with this:

1. we are dropping support for py39
2. but we still have support for 310->314 since we use abi310
   ?

[HuggingFaceDocBuilderDev]

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

[ngoldbaum]

we are dropping support for py39
but we still have support for 310->314 since we use abi310
?

Exactly! See https://pyo3.rs/v0.28.2/building-and-distribution.html#minimum-python-version-for-abi3

[ngoldbaum]

Also, for what it's worth, I'm looking at adding a section to PEP 803 with quotes from library maintainers.

If you wouldn't mind, I'd appreciate it if I could include your opinion about the need for a stable ABI that supports the free-threaded build. Accepting PEP 803 will ensure that such a thing exists for Python 3.15 and I'd like to make that case as strong as possible.