fix(runtime): remove stale harness 0.4 constraints

[kjgbot]

Summary

• widen harness compatibility metadata for continuation, telemetry, turn-context, and webhook-runtime
• bump harness to depend on turn-context 0.3.x so fresh installs stop nesting the old 0.4.x graph
• repoint cloudflare-runtime to the new continuation/webhook-runtime releases so cloud can drop temporary overrides after publish

Why

Cloud PR #364 needed root overrides because published package metadata still pulled @agent-assistant/harness@^0.4.x through telemetry, turn-context, continuation, webhook-runtime, and cloudflare-runtime/harness transitive edges.

This change makes the published graph resolve cleanly on harness 0.6.x for fresh installs while preserving compatibility ranges where appropriate.

Verification

• npm install --no-audit --no-fund
• npm run build -w @agent-assistant/harness -w @agent-assistant/continuation -w @agent-assistant/telemetry -w @agent-assistant/turn-context -w @agent-assistant/webhook-runtime -w @agent-assistant/cloudflare-runtime
• npm test -w @agent-assistant/harness -w @agent-assistant/continuation -w @agent-assistant/telemetry -w @agent-assistant/turn-context -w @agent-assistant/webhook-runtime -w @agent-assistant/cloudflare-runtime
• packed tarballs for harness/continuation/telemetry/turn-context/webhook-runtime/cloudflare-runtime and verified in a clean temp install that @agentworkforce/sage@1.5.1 resolves to harness 0.6.4 with no nested 0.4.x copy

Follow-up

After these packages are published, cloud PR #364 can pin @agentworkforce/sage to 1.5.1, remove the temporary harness overrides, regenerate package-lock.json, and rerun CI.