Override range to avoid patching pubgrub

[konstin]

Create a newtype struct PubGrubRange(pubgrub::range::Range<Version>) to avoid overriding the Display implementation on Range in pubgrub itself, reducing our diff with upstream. Used methods taking an &Self or returning Self were overridden, the rest of the methods succeeds through deref.

An additional advantage is that we can start using the range type in more places without depending on pubgrub directly (#4041).

The alternative would be moving range formatting into the error formatter, but this would make pubgrub's api strange, deviating from rust's Display standard.

[zanieb]

We discussed this in Discord and we both think this is a lot of boilerplate and a bit of an ugly solution but I don't think there's a better way if you want the ergonomics of Display. The alternative is probably relying on a PubGrub formatter method that we call into explicitly? I am not sure resolving this divergence from upstream is necessarily worth the added code here. It seems like we'd be taking on more maintenance burden to keep our wrapper type up to date. However, @konstin mentioned wanting to use PubGrub ranges outside the resolver which may justify the effort?

[zanieb]

@konstin can we close this?

cc @BurntSushi I feel like we were recently talking about using Range outside the resolver

[BurntSushi]

I hadn't seen this PR before.

Personally, I think the added code here is fine and I think it's worthwhile to reduce our pubgrub diff as much as possible with upstream.

With that said, my understanding is that we want to use something like a pubgrub Range outside of uv-resolver in uv-pep508 for the MarkerTree implementation. I believe there was talk of making a new crate that both upstream pubgrub depends on and we depend on that exposes a Range type.