fix: ensure sandbox-agent is on PATH in Compute SDK sandbox

[kisernl]

This pull request introduces a new example for running the sandbox-agent inside a ComputeSDK sandbox, demonstrating how to use ComputeSDK as a unified interface for multiple cloud sandbox providers. It adds all necessary documentation, example code, tests, and project configuration for the new example, and updates the monorepo dependencies to include ComputeSDK and related packages.

Major additions and changes:

New ComputeSDK Example:

• Added a new example project in examples/computesdk that demonstrates how to deploy and interact with the sandbox-agent using ComputeSDK. The example includes TypeScript code to create a sandbox, install and start the agent, run a prompt, and clean up resources. [1] [2] [3]
• Added an automated test (computesdk.test.ts) to verify that the sandbox-agent starts correctly in a ComputeSDK sandbox and responds to health checks.

Documentation:

• Added a new documentation page (docs/deploy/computesdk.mdx) explaining ComputeSDK, prerequisites, usage examples, provider flexibility, and supported providers.

Dependency and Monorepo Updates:

• Added computesdk, dotenv, and related dependencies to the monorepo and the new example’s package.json. Updated pnpm-lock.yaml to reflect these dependencies and their versions. [1] [2] [3] [4] [5] [6] [7]
• Updated TypeScript and Node.js type dependencies across the monorepo to ensure compatibility with the new example and ComputeSDK. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13]

These changes provide a ready-to-use example and test for ComputeSDK integration, making it easier for users to deploy the sandbox-agent across multiple cloud providers with minimal code changes.