Allow passing packages to `--excludes` option

[terror]

There are cases where users may want to exclude a single package, but end up having to write it to a file in order to do so, which I find a bit awkward. We should consider allowing --excludes for pip {compile, install, tool install} to accept package names alongside actual paths.

For instance, the following flow:

uv self update
echo xformers > exclude.txt
uv pip install -U vllm --extra-index-url [https://wheels.vllm.ai/nightly](https://t.co/Y5FwbIWlUu) --excludes exclude.txt

would become:

uv self update
uv pip install -U vllm --extra-index-url [https://wheels.vllm.ai/nightly](https://t.co/Y5FwbIWlUu) --exclude xformers

This may be a bit tricky to implement, since it will likely require us to make a guess as to what argument is a path or a package name.

[zanieb]

I think we'll probably want a separate argument, e.g., --exclude-package, to avoid disambiguating between paths and names? In general, I think we want this functionality for constraints, excludes, and overrides so we'll want something coherent amongst them.

Unfortunately we named this exclude-dependencies (etc.) in the pyproject.toml, but we could consider rename that at some point too.

We could also consider changing the existing arguments, first using inference to determine if it's a file or name then deprecating one of the paths. e.g., --constraint <requirement> or --exclude <package> could be the long-term goal and we could add a --constraint-file and --exclude-file that we encourage users to use instead for the file option.

[charliermarsh]

Another option would be like...

--exclude-package ${packageName} on the CLI, exclude-packages in the pyproject.toml, and then --excludes ${filePath} for a list from a file.

--constraint-package ${packageName}>=1 on the CLI, constraint-packages in the pyproject.toml, and then --constraints ${filePath} for a list from a file.

[terror]

Should we also consider --exclude-packages ${packageName} ... ${packageName} and --constraint-packages ${packageName}>=1 ... ${packageName}>=1 on the CLI? I mention the single package case in the issue, but this might also apply to 2 or 3 or more (i.e. a small amount).

[zanieb]

We generally can't use space delimited names in the CLI because it creates ambiguous parsing. We usually prefer ,. There are various places where we allow this (and I'd expect to here)