Fix version of pip with wrong python constraints

[traversaro]

Fix part of conda-forge/pip-feedstock#132 .

Checklist

• Used a static YAML file for the patch if possible (instructions).
• Only wrote code directly into generate_patch_json.py if absolutely necessary.
• Ran pre-commit run -a and ensured all files pass the linting checks.
• Ran python show_diff.py and posted the output as part of the PR.
• Modifications won't affect packages built in the future.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

[traversaro]

diff:

================================================================================
================================================================================
linux-armv7l
================================================================================
================================================================================
linux-ppc64le
================================================================================
================================================================================
linux-aarch64
================================================================================
================================================================================
noarch
noarch::pip-24.3.1-pyh145f28c_1.conda
-    "python >=3.9"
+    "python >=3.13.0a0"
================================================================================
================================================================================
win-32
================================================================================
================================================================================
osx-arm64

[h-vetinari]

Should we not add wheel and setuptools then?

[traversaro]

It is correct for pip not to have wheel and setuptools if installed with python>=3.13, see conda-forge/pip-feedstock#126 . The problem is that this build was meant to be installed only for python>=3.13, but this specific build did not have this constraint. This repodata patch remove the incorrect run constraint python >=3.9 and adds the correct one python >=3.13.0a0 (see also the output of show_diff script).

[h-vetinari]

OK, you're right, I had gotten it mixed up how things should have been vs. how they were vs. how to undo the damage. 😅