[python3Packages.]uv: Remove dependencies on cmake and pkg-config

[bengsparks]

There are no references to cmake in the entire project, but these dependencies have been included in the package since it was first added in 29a6185. The relevant PR #289151 does not include a rationale for this, and even back then, the repository at the time did not include CMakeLists.txt or *.cmake files.
Perhaps this was due to historical reasons, but nowadays there is no need for it :)

I've also added versionCheckHook to the Python package, so that inherit (pkgs.uv) versionCheckProgramArg; actually does something for the package.
Finally I've added myself to the maintainer list of uv, as I get to use uv from nixpkgs at work, and also responsible for the uv-build package, which inherits a fair amount from uv.

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[Prince213]

Please put the maintainer commit before rest of your changes. See https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#commit-conventions.

[bengsparks]

When adding yourself as maintainer in the same pull request, make a separate commit with the message maintainers: add <handle>.
Add the commit before those making changes to the package or module. See Nixpkgs Maintainers for details.

@Prince213 I believe the convention you are referring to is about adding oneself to the maintainer-list.nix, then adding the new handle to the maintainers list of a package.
The commit conventions clue in on this by requiring a maintainers: prefix, and not specifying the package at all, which would be wrong here.

[bengsparks]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 407665 --skip-package-regex home-assistant.*

---

aarch64-darwin

⏩ 4 packages marked as broken and skipped:

• python312Packages.bentoml
• python312Packages.bentoml.dist
• python313Packages.bentoml
• python313Packages.bentoml.dist

✅ 9 packages built:

• hatch
• hatch.dist
• prefect
• prefect.dist
• python312Packages.uv
• python312Packages.uv.dist
• python313Packages.uv
• python313Packages.uv.dist
• uv

[Prince213]

@Prince213 I believe the convention you are referring to is about adding oneself to the maintainer-list.nix, then adding the new handle to the maintainers list of a package. The commit conventions clue in on this by requiring a maintainers: prefix, and not specifying the package at all, which would be wrong here.

I still feel that both changing maintainer-list.nix and maintainers of a package should come before any other changes. But it's not a explicit requirements I think.

[Prince213]

Otherwise Diff LGTM

[GaetanLepage]

Thanks!