Supporting `uv` configuration about pixi

[tdejager]

Thanks @zen-xu this is the PR I mentioned: #1986

[baszalmstra]

I think it would be possible for us to port most of these over. But Ill let @tdejager chime in here. :)

[tdejager]

Yes we can port most of these over, I've already started on index-strategy actually.

To explain a bit better why this is taking some time:
Ideally you would just rust import the uv options and use these directly, without requiring a translation on our side. However, as I see it, and feel free to convince me otherwise, we currently cannot. Because of the following reasons:

1. We sometimes do not want to expose the option (pretty rare), but we opted to only do build isolation per package for example.
2. We need to make decisions to make them work nicely with environments.
3. We might have different reasons for breaking compatibility, by relying on these options directly we are essentialy tied in that respect to uv's release cycle. We might want to deprecate an option more slowely for example.
4. Finally and most important a lot of these options are part of the pixi_manifest crate, as uv does not publish on crates.io I do not want a git dependency in there, as there is a big chance we want to publish this crate in the future.

This makes it so it takes a little more time to add these options, sorry about that, but anyone reading it feel free to request any that you are missing.

Hope this gives a bit of insight. Thanks for the issue!

[zen-xu]

Thank @tdejager for your reply, I agree with your points, but I believe that any incompatibility resulting from users configuring uv options is the user's own responsibility (give a warning?), and the Pixi team does not need to handle these compatibility issues