Track priorities in a set and allow updating from uv

[konstin]

In uv, we were updating package priorities without syncing them uv, so uv and pubgrub were getting out of sync. We couldn't previously do this because the way priority updates were done. Instead, we switch to tracking the packages whose derivations changed in a set, based on pubgrub-rs/pubgrub@dev...Eh2406:pubgrub:stop-prioritize. Since uv priorities don't depend on the ranges, we can speed this up further by not using this set in uv. In pubgrub, we can upstream this and use it as a correctness fix to also reprioritize when the conflict tracker changed, which is currently not handled.

Also exposes into_raw since we start using it on the uv side.

[codspeed-hq]

CodSpeed Performance Report

Congrats! CodSpeed is installed 🎉

🆕 6 new benchmarks were detected.

You will start to see performance impacts in the reports once the benchmarks are run from your default branch.

Detected benchmarks

• backtracking_disjoint_versions (2.4 s)
• backtracking_ranges (2 s)
• backtracking_singletons (4.5 s)
• large_case_u16_NumberVersion.ron (25.4 ms)
• sudoku-easy (3.7 ms)
• sudoku-hard (4.2 ms)

[Eh2406]

seems like we could directly iterate over prioritized_potential_packages and outdated_priorities instead of iterating over all of package_assignments. I think this method is only used by UV, so not sure what semantics you need.

[konstin]

we use this to make prefetches, and i think currently in a kind of inefficient way. we need to emit a prefetch at least the first time we see a package, and at most when its range changes; the previous and this was good enough in profiling for now.