feat(api)!: use sandbox names as canonical RPC references

[drew]

Summary

Standardize public sandbox references on the human-readable sandbox name. Every sandbox-scoped gateway RPC now accepts a string sandbox with workspace selection carried separately, while canonical sandbox IDs remain internal metadata for authentication, persistence, and compute-driver boundaries.

Related Issue

Closes #3050

Changes

• Replace the temporary SandboxReference wrapper and public ID references with sandbox strings.
• Resolve names at the gateway and authorize the persisted sandbox workspace without exposing cross-workspace existence.
• Reserve removed protobuf ID fields and preserve existing name-field wire tags where possible.
• Update the CLI, TUI, Rust core and SDK, gateway interceptors, Python SDK, Go SDK, TypeScript SDK, examples, generated bindings, tests, and documentation.
• Carry sandbox names through SSH and TCP forwarding while retaining IDs only for internal lifecycle metadata.

Testing

• mise run pre-commit passes
• Unit tests added/updated
• E2E tests added/updated (not applicable; no running gateway environment was used)
• cargo test -p openshell-server with an isolated system gateway directory (1,463 tests)
• cargo test -p openshell-cli -p openshell-tui
• mise run sdk:ts:ci (105 tests)
• uv run --frozen pytest python/openshell/sandbox_test.py (130 tests)
• Relevant Go SDK packages pass, and build, lint, formatting, docs, and protobuf checks pass
• Full mise run go:ci (three unrelated gateway-discovery tests observe /etc/openshell/gateways/default on this development host)

Checklist

• Follows Conventional Commits
• Commits are signed off (DCO)
• Architecture docs updated (if applicable)

[github-actions]

🌿 Preview your docs: https://nvidia-preview-pr-3272.docs.buildwithfern.com/openshell

[copy-pr-bot]

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

[elezar]

Does this mean that the workspace, sandbox name are the unique identifier for the sandbox? (If I recall correctly, I saw an issue where users in different workspaces can delete / access a sandbox if they create one with the same name. Does this solve that?).