Avoid overwriting dependencies with different markers in uv add

[blueraft]

Summary

Splitting out #6005

Test Plan

cargo test

[zanieb]

Not sure if this is covered, but we'll probably want uv remove foo to remove all dependencies on foo regardless of the markers?

[ibraheemdev]

Haven't read the PR in detail yet, but if there is only a single instance of the package name can we update it regardless of the markers (without overwriting them if unspecified)? For example, uv add requests; os_name == 'Linux' followed by uv add requests==2.0.0: should the original dependency be updated or should we add a new entry?

[zanieb]

For example, uv add requests; os_name == 'Linux' followed by uv add requests==2.0.0: should the original dependency be updated or should we add a new entry?

Hard choice here — but if we update the existing entry here then there's no way to add a dependency without a marker so I think we need to add a new entry.

[blueraft]

Not sure if this is covered, but we'll probably want uv remove foo to remove all dependencies on foo regardless of the markers?

It should be covered now.

For example, uv add requests; os_name == 'Linux' followed by uv add requests==2.0.0: should the original dependency be updated or should we add a new entry?

I agree with Zanie. If we were to update, we would also have to consider version comparisons before updating. uv add requests==2.30; os_name == 'Linux' followed by uv add requests>=2.0.0 should create an additional entry.

[blueraft]

Hm something went wrong with Github Actions there, why is it building the docker image? 🤔

[zanieb]

Thanks!