build(deps): update grpcio-tools requirement from >=1.81.1 to >=1.82.1

[dependabot]

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: dependencies, python. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[drunkcoding]

Blocked: conflicts with the protobuf<7 constraint

This bump can't be merged as-is. The Resolve Python dependencies (dry-run) CI step fails with a hard resolver conflict:

ERROR: Cannot install -r requirements.txt (line 4) and protobuf<7,>=4.21.6
       because these package versions have conflicting dependencies.
The conflict is caused by:
    grpcio-tools 1.82.1 depends on protobuf<8.0.0 and >=7.35.1
ERROR: ResolutionImpossible

Root cause: grpcio-tools 1.82.1 now hard-requires protobuf>=7.35.1,<8, but this project pins protobuf<7 to stay aligned with the vendored external/protobuf/ (see CLAUDE.md §5/§10 — protobuf is treated as a wire-contract dependency and not bumped without review).

Note: the recently merged #89 raises the protobuf floor to >=6.33.6 but deliberately keeps <7, so it does not unblock this PR.

What's needed to unblock: a deliberate protobuf-7 migration — bumping the vendored C++ protobuf and the Python protobuf pin to >=7 together, then re-validating the wire format and re-running the Docker test suite. That's a coordinated change beyond a routine dependency bump.

Leaving this open as a tracker for that migration rather than closing it.

[dependabot]

Superseded by #101.