updating resolvelib version to include new reporter interface

[nadavwe]

a prerequisite for #10258

[uranusjr]

Needs a news entry for the vendor update, otherwise lgtm.

[pradyunsg]

We should update the debugging reporter as well.

[uranusjr]

I think the idea is to only update vendoring in this PR and do all the pip changes in #10258 (that PR does change the debugging reporter).

[pradyunsg]

Ah, cool. Ignore me -- I'm just being noisy then. :)

[nadavwe]

Needs a news entry for the vendor update, otherwise lgtm.

I kinda knew I should add that... but wasn't sure what to write. I should have looked into another vendor upgrade before submitting.
How would you feel if I open a PR for _vendor/README.rst to include a paragraph on the news, so other people can just follow that readme when upgrading?

[uranusjr]

Don't need to update README, this is fine.

[nadavwe]

How would you feel if I open a PR for _vendor/README.rst to include a paragraph on the news, so other people can just follow that readme when upgrading?

@uranusjr I think I did not make myself clear on this point. ⬆️
I did not mean to add news on the upgrade of resolvelib in _vendor/README.rst. (that, of course, would be quite silly).
I meant adding a section like:
"you should add a news piece when syncing vendored packages. it should look something like..." etc.

[uranusjr]

This is already mentioned in the documentation:

https://pip.pypa.io/en/stable/development/contributing/#choosing-the-type-of-news-entry

Which I think is more visible than pip/_vendor/README.rst. But I guess it wouldn't hurt adding a line there as well to tell the contributor to refer to documentation.

[uranusjr]

Anyway, this should be good since the static checks passed. Let's deal with this in another issue or PR.