[rollout] fix: add missing orjson runtime dependency

[JoyboyBrian]

What

• Add orjson>=3.11.6,<4.0 as a direct SDK runtime dependency for tool-enabled rollout calls across local and remote backends.
• Regenerate uv.lock, resolving orjson==3.11.9.

Why

Tool-enabled rollout calls can fail on any backend that installs the base SDK dependency set without separately installing orjson. This affected both LocalBackend and Harbor/Daytona sandbox execution, failing with litellm.APIConnectionError: OpenAIException - No module named 'orjson'.

LiteLLM imports LiteLLM_Proxy_MCP_Handler whenever a completion contains any tools (v1.92.0 source). LiteLLM PR #31576 added a top-level LiteLLMProxyRequestSetup import to that handler (commit), which imports http_parsing_utils and therefore orjson at module load time. LiteLLM still declares orjson only under its proxy optional extra (pyproject.toml), so a base LiteLLM installation can reach this runtime path without having orjson installed.

Declaring orjson directly with LiteLLM's existing version bound makes the SDK dependency set complete for tool-enabled rollout calls across local and remote backends. Adding orjson to the rollout image also unblocked the failed remote evaluation and artifact collection, confirming that the dependency gap—not artifact persistence—caused that incident.

How to Test

• uv lock --check
• uv run --locked --extra dev ruff check .
• uv run --locked --extra dev ruff format --check .
• uv run --locked --extra dev pyright osmosis_ai/
• uv run --locked --extra dev pytest -q
• uv build --wheel --out-dir /tmp/osmosis-sdk-orjson-dist
• unzip -p /tmp/osmosis-sdk-orjson-dist/*.whl '*/METADATA' | rg '^Requires-Dist: orjson'

Checklist

• PR title follows [module] type: description format
• Appropriate labels added (bug, rollout, dependencies)
• ruff check . and ruff format --check . pass
• pyright osmosis_ai/ passes
• pytest passes (1607 passed)
• Public API changes are documented (no public API changes)
• No secrets or credentials included

[cubic-dev-ai]

No issues found across 2 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Re-trigger cubic}