Bump problematic dependencies to avoid backtracking

[potiuk]

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[jscheffl]

Let's see!

[jscheffl]

What is your approach for such selection? Taking the package with the most number of releases since the lower pin you find in the repo?

[potiuk]

What is your approach for such selection? Taking the package with the most number of releases since the lower pin you find in the repo?

Pure guessing. .. Maybe @notatallshaw might have some better hints? FYI @notatallshaw -> we again had problems with backtracking with pip -> https://github.com/apache/airflow/actions/runs/15647299212/job/44088044699#step:9:5090

[potiuk]

Added pypa/pip#13281 (comment) -> maybe Damian will be able to help again.

[notatallshaw]

FYI I can reproduce it and am taking a look, no promises, but if I can find a solution I will open a PR.

[potiuk]

🙇 🙇

[notatallshaw]

Btw, I've also merged sarugaku/resolvelib#188 which I hope to get in to pip 25.2.

This will restore the biggest optimization, for most cases, that was available in 25.0 and lost in 25.1.

25.1 also added several other optimizations, and I am experimenting with an additional optimization which I think will particularly benefit Airflow's CI, so I'm hopeful 25.2 will be a lot less problematic for you.

[notatallshaw]

@potiuk PR available #51742