chore(release): bump version to 0.4.4

[appcypher]

TL;DR

Bump every microsandbox crate, the node-ts and Python SDKs, the mcp submodule, and the TypeScript example pins from 0.4.3 to 0.4.4 in preparation for the next release.

Description

• Workspace Cargo.toml and all internal microsandbox-* path-dep version pins moved to 0.4.4 (cli, microsandbox, runtime, network, image, filesystem, agentd).
• node-ts SDK package version, three npm/<target>/package.json binaries, package-lock.json, and the native/index.cjs version-check guards updated to 0.4.4.
• Python SDK and node-ts SDK Cargo manifests bumped to depend on microsandbox 0.4.4 and microsandbox-network 0.4.4.
• mcp submodule pointer advanced to its own 0.4.4 bump (server version, package version, and microsandbox dep).
• All 15 TypeScript example package.json files plus the three checked-in package-lock.json files (init-handoff, logs-read, shell-attach) bumped from 0.4.3 to 0.4.4.
• Cargo lockfiles regenerated for both the workspace and the standalone crates/agentd workspace.

Changelog since v0.4.3:

• feat(agentd): hand off PID 1 to a guest init binary (feat(agentd): hand off PID 1 to a guest init binary #653)
• feat(snapshot): file-first disk snapshots across cli, rust, ts, python (feat(snapshot): file-first disk snapshots across cli, rust, ts, python #652)
• feat(logs): exec.log capture, boot-error.json, typed ExecFailed (feat(logs): exec.log capture, boot-error.json, typed ExecFailed #650)
• fix(net): --no-net actually air-gaps the guest (fix(net): --no-net actually air-gaps the guest #647)
• fix(node-sdk): ship libkrunfw under canonical name in npm platform package (fix(node-sdk): ship libkrunfw under canonical name in npm platform package #648)

Test Plan

• cargo build --workspace exits 0
• cargo build inside crates/agentd exits 0
• npm publish --dry-run in sdk/node-ts reports microsandbox@0.4.4
• npm publish --dry-run in mcp reports microsandbox-mcp@0.4.4
• grep -r '"0\.4\.3"' . returns no microsandbox-related hits