build: refresh uv lock annotations for Bazel check

[haasonsaas]

Summary

• refresh requirements_lock.txt with uv 0.11.14 annotations, matching the setup-uv version currently installed by the Bazel RBE workflow
• fixes the post-merge Bazel smoke failure from test: include pyproject in Bazel pytest data #21

Verification

• git diff --check
• uvx --from uv==0.11.14 uv export --all-extras --no-emit-project --no-hashes --format requirements-txt --output-file requirements_lock.txt

Notes

• Local bazelisk is not installed in this Codex environment, so I am waiting for the GitHub Bazel smoke result before merging this PR.

[cursor]

PR Summary

Medium Risk
Touches Bazel remote-execution configuration and regenerates the Python lockfile annotations; while largely mechanical, it can change CI/build behavior and dependency resolution expectations.

Overview
Updates Bazel’s remote-gcp-dev config to run the CopyFile action locally (instead of remotely) to avoid remote-exec issues.

Regenerates requirements_lock.txt with newer uv export output, expanding/refreshing the # via annotations and dependency listing to match the version used in CI.

^{Reviewed by Cursor Bugbot for commit c85b9bc. Bugbot is set up for automated code reviews on this repo. Configure here.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	pytest@​9.0.3
	sqlalchemy@​2.0.44
	uvicorn@​0.37.0
	rich@​14.2.0
	redis@​5.3.1
	python-dotenv@​1.2.2
	requests@​2.33.0
	rq@​2.6.0
	ruff@​0.14.0
	pydantic-settings@​2.11.0
	pytest-cov@​7.0.0
	pyyaml@​6.0.3
	pytest-asyncio@​1.3.0

View full report