Build a Daytona sandbox image at runtime with the declarative Image builder, without a Dockerfile or registry push

Documented steps

1. Import the `Image` class from the Daytona SDK.
2. Pick a base: `Image.debian_slim('3.12')` (TypeScript `Image.debianSlim`) for a Debian slim base with a chosen Python version, or `Image.base('python:3.12-slim-bookworm')` for any custom base image.
3. Add Python dependencies by chaining `.pip_install(['requests','pandas'])`, `.pip_install_from_requirements('requirements.txt')` or `.pip_install_from_pyproject('pyproject.toml', optional_dependencies=['dev'])`.
4. Add arbitrary build steps with `.run_commands('apt-get update && apt-get install -y git')` or inject raw Dockerfile instructions with `.dockerfile_commands([...])`.
5. Copy local content in with `.add_local_file('package.json', '/home/daytona/package.json')` and `.add_local_dir('src', '/home/daytona/src')`.
6. Configure runtime with `.env({...})`, `.workdir('/home/daytona')`, `.entrypoint([...])` and `.cmd([...])`.
7. Chain system operations into a single command (`apt-get update && apt-get install -y ... && rm -rf /var/lib/apt/lists/*`) to minimise layers.
8. Create a sandbox straight from the in-memory image: Python `daytona.create(CreateSandboxFromImageParams(image=declarative_image), timeout=0, on_snapshot_create_logs=print)`; TypeScript `await daytona.create({ image }, { timeout: 0, onSnapshotCreateLogs: console.log })`.
9. Stream the build logs through the `on_snapshot_create_logs` / `onSnapshotCreateLogs` callback so build failures are visible rather than surfacing as a create timeout.
10. When the same image will back many sandboxes, promote it to a named snapshot with `daytona.snapshot.create(CreateSnapshotParams(name='snapshot_name', image=declarative_image), on_logs=print)` and create from the snapshot thereafter. Official docs: https://www.daytona.io/docs/en/declarative-builder, https://www.daytona.io/docs/en/snapshots