[pygments] Upgrade pip to fix broken build

[DaveLak]

It looks like the pygments build has the same toml parsing issue as I described in c3bedd8, i.e. the outdated pip was unable to parse pyproject.toml syntax.

But curiously, the this hasn't been an issue until the most recent (at the time of writing) build on 2024-03-30 log and prior builds (e.g. 2024-03-29 log) listed on https://oss-fuzz-build-logs.storage.googleapis.com/index.html#pygments seem to have been fine?

I wonder if something changed somewhere and more projects that don't upgrade pip will begin failing?

In any case, this fixes the build. Tested locally with python infra/helper.py check_build pygments.

[github-actions]

DaveLak is a new contributor to projects/pygments. The PR must be approved by known contributors before it can be merged. The past contributors are: jvoisin, Google-Autofuzz, TheShiftedBit, fmeum, birkenfeld

[maflcko]

cc @jvoisin

[jvoisin]

Shouldn't this be fixed in the base image, instead of having to add the same line in every python project when the issue arises?

[DaveLak]

Shouldn't this be fixed in the base image, instead of having to add the same line in every python project when the issue arises?

Yes, I think so, and #11420 looks like it would do just that (in addition to resolving other Python dependency issues, e.g., #11742.

However, given the complexity of the ongoing clang-18 upgrade in #11714, the change proposed here felt like the best way to keep pygments fuzzers productive until the dust settles and bandwidth is available to introduce a more comprehensive solution.

[jvoisin]

Those hacks will stay in place even after clang-18 happens, but I guess the amount of resources consumed by upgrading pip is negligible compared to running fuzzers, so LGTM.