pre-commit uv lock check (#2932)

<!--
Thanks for opening a pull request!
-->

<!-- In the case this PR will resolve an issue, please replace
${GITHUB_ISSUE_ID} below with the actual Github issue id. -->
<!-- Closes #${GITHUB_ISSUE_ID} -->

# Rationale for this change
In #2928, the `uv.lock` wasn't generated correctly after a dependency
change.
Adding the following changes:
1. `make uv-lock` to generate one when modifying dependencies
2. `make uv-lock-check` to check if the `uv.lock` is up to date
3. Adding a pre-commit config to check the `uv.lock` and fail if not
updated correctly (uses 2.)
4. Documentation change in `mkdocs/docs/contributing.md` to add
instructions for contributors.

## Are these changes tested?
Locally.
Added some of the dependencies in #2928 without modifying the lock file
and ran `pre-commit run --all-files` to observe the following failure
message
```
uv lock file check.......................................................Failed
- hook id: uv-lock-check
- exit code: 2

uv lock --check 
Resolved 221 packages in 93ms
The lockfile at `uv.lock` needs to be updated, but `--check` was provided. To update the lockfile, run `uv lock`.
make: *** [uv-lock-check] Error 1
```

## Are there any user-facing changes?
No. Useful for contributions that change versions/ dependencies.

Author: nssalian

.pre-commit-config.yaml

@@ -70,3 +70,11 @@ repos:
     rev: v2.4.1
     hooks:
       - id: codespell
+  - repo: local
+    hooks:
+      - id: uv-lock-check
+        name: uv lock file check
+        entry: make uv-lock-check
+        language: system
+        pass_filenames: false
+        files: ^(pyproject\.toml|uv\.lock)$

Makefile

@@ -168,3 +168,11 @@ clean: ## Remove build artifacts and caches
 	@find . -name "*.pyd" -exec echo Deleting {} \; -delete
 	@find . -name "*.pyo" -exec echo Deleting {} \; -delete
 	@echo "Cleanup complete."
+
+uv-lock: ## Regenerate uv.lock file from pyproject.toml
+	uv lock $(PYTHON_ARG)
+
+uv-lock-check: ## Verify uv.lock is up to date
+	@command -v uv >/dev/null || \
+	  (echo "uv is required. Run 'make install' or 'make install-uv' first." && exit 1)
+	uv lock --check $(PYTHON_ARG)

mkdocs/docs/contributing.md

@@ -90,6 +90,23 @@ For full control over your environment, you can use uv commands directly. See th
 - Running commands with `uv run`
 - Lock file management with `uv.lock`
 
+### Lock File Management
+
+`uv.lock` is a cross-platform lockfile that contains exact information about the project's dependencies.
+See the [uv.lock documentation](https://docs.astral.sh/uv/guides/projects/#uvlock) for more details.
+
+When modifying dependencies in `pyproject.toml`, regenerate the lock file:
+
+```bash
+make uv-lock
+```
+
+Separately, to verify that the lock file is up to date without modifying it:
+
+```bash
+make uv-lock-check
+```
+
 ## Installation from source
 
 Clone the repository for local development: