VS Code format-on-save currently queries Bazel on every invocation, so concurrent builds can stall editor saves. Update `buildscripts/clang_format_vscode.sh` to validate a cached or downloaded formatter against `buildscripts/clang_format_version.txt` and execute it directly. Initial setup bypasses the repository wrapper and uses `--noblock_for_lock` so a busy Bazel server fails immediately.

Add the `lint.clang-format-version` check: on Linux, `bazel run lint` verifies the pin against Bazel's native formatter and prepares the editor cache; `bazel run lint --fix` updates the pin. Version probes reject stale binaries while preserving editor arguments, stdin, diagnostics, and exit status. Document setup and toolchain updates in `bazel/docs/developer_workflow.md`.

Ticket: https://jira.mongodb.org/browse/SERVER-136913

Validation: `bazel run format`; 89 Python unit tests; both Bazel formatter test targets; the new lint check against the real pinned toolchain. Coverage includes busy Bazel, branch/pin changes, replacement or deletion of cached binaries, and formatter I/O. Standalone Ruff found existing findings in the quality-check files; the new helper and formatter test files pass.