Vendoring updates for 23.1

[pfmoore]

Skips pygments, tenacity and setuptools, as they all need updates to the patches. @pradyunsg can you take a look please?

[pfmoore]

It's not going to be my day, I can see. If the "Create RAMDisk" step is failing, I refuse to believe that's my fault. I'll let all the other checks run, and then try re-running the failed one in case the issue is intermittent, rather than a problem with the Windows worker.

[pradyunsg]

I think Github changed something about the environment that broke RAM disks for us (again).

[sbidoul]

I've seen these RAM disk errors more frequently recently. Usually restarting the failed jobs is sufficient, which I just did here.

[pfmoore]

I sorted out the setuptools patch (I think) so I added that.

[pfmoore]

... and tenacity.

@pradyunsg All I did was:

1. Try to do the revendor. That leaves a bunch of uncommitted stuff in my working directory.
2. Manually review the patch and edit it to match the changed source. This involved editing the surrounding text that no longer matched, and/or changing line numbers in the header.
3. Save the change to the patch file and revert everything else that was changed by the vendoring run.
4. Cross fingers and re-run the vendoring.

Is that basically correct? I really don't like manually editing patch files, but given all of the changes in the working copy, editing the file and doing git diff wasn't an option as far as I could see...

[pfmoore]

... and that's pygments done. So I think I now have all of the vendoring done for 23.1, assuming nothing else changes before the release.

[sbidoul]

Is this change intentional? ("Update pkg_resources (via setuptools)" becoming "Upgrade setuptools")

[pradyunsg]

I think it's a consequence of the automation handling things slightly differently than the manual upgrade I'd done earlier!

[pfmoore]

That's what I assume - I certainly didn't do anything explicit to cause this to happen.

[sbidoul]

LGTM