Support uv.lock in the Gazelle plugin

[aaronsky]

Support uv.lock in the Gazelle plugin

Relevant Rules

gazelle_python_manifest in //gazelle/manifest:defs.bzl

Description

The changes in #3952 to support #1975 have been helpful so far, thank you! I wanted to know if it would be possible to support uv_lock as an attr on gazelle_python_manifest as well, so that I can completely delete our requirements.lock.txt.

Describe the solution you'd like

Anything that will allow me to provide either uv_lock as an attr on gazelle_python_manifest instead of requirements, or something to totally obviate the manifest (as some other Gazelle plugins have managed to accomplish).

Describe alternatives you've considered

I haven't considered any alternatives, and I'm not super familiar with the constraints of this system (outside of having written a narrow Gazelle plugin of my own), so open to suggestions on the best way to approach this.

[aignas]

The requirements file is there to just calculate integrity, you can pass any file or omit passing the file altogether.

So the expected fixes here are:

• Deprecate the old name of the attr.
• Add a new attr called lockfiles.
• Add documentation about this.
• (optional) rename the CLI args to the manifest generator.

Code: https://github.com/bazel-contrib/rules_python/blob/main/gazelle/manifest/manifest.go#L31