Create a process for releasing a wheel for a new Python version with a previous sklearn version on CI

For version 1.5.2, the wheels were not updated from the CI, but from an API key. Moving forward, I think we should update our CI to allow us to push specific python versions. I propose this process:

1. Prerequisite: Python 3.14rc support added to cibuildwheel + numpy & scipy has wheels for it
2. Update build_tools/cirrus/arm_wheel.yml and .github/workflows/wheels.yml to support the new version on 1.X.X branch
3. Trigger .github/workflows/publish_pypi.yml (workflow_run) with a specific python version which will only upload wheels for that python version.

These are the tasks I see:

• Required: Update .github/workflows/publish_pypi.yml to accept a specific python version and only upload that python version.
• Nice to have, but not required: build_tools/cirrus/arm_wheel.yml and .github/workflows/wheels.yml to only build wheels for a specific python version.

CC @lesteve

Start by reading .github/workflows/publish_pypi.yml, then compare the Python-version handling in build_tools/cirrus/arm_wheel.yml and .github/workflows/wheels.yml. Verify how workflow_run is triggered and how a specific Python version is selected. Done means the publish workflow accepts a requested version and uploads wheels only for that version; the other workflow updates are optional.