Use --no-build-isolation for uv build after sync

[Owen-Liuyuxuan]

Summary

• CI, docs deploy, and Cloudflare Pages builds now run uv build with --no-build-isolation so Hatch protobuf codegen uses the locked .venv from uv sync instead of re-resolving newer protobuf / mypy-protobuf in an isolated PEP 517 env.
• Production build docs now require uv sync --all-packages before uv build --all-packages --no-build-isolation.

Test plan

• uv sync --all-extras --dev --all-packages
• Baseline: isolated uv build --package sync-tooling-msgs selected protobuf 6.33.6 / mypy-protobuf 5.1.0 (venv had 6.33.4)
• After fix: uv build --package sync-tooling-msgs --no-build-isolation uses venv (no re-resolve Selecting lines)
• uv build --package sync-tooling-msgs --no-build-isolation -o /tmp/dist-test succeeds
• uv build --all-packages --no-build-isolation succeeds
• CI workflow on this PR

Made with Cursor

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Owen-Liuyuxuan]

Superseded by ground-up fix: unify protobuf codegen with uv.lock at uv sync via build-constraint-dependencies (PR #38 rework).