Unify package names and upgrade Rust and JavaScript dependencies

[lukebuehler]

This consolidates the greenfield package names and upgrades the JavaScript and Rust dependency stacks, with builds, generated consumers, release packaging, and documentation aligned to the new names.

• Rename engine to harness, temporal-server to temporal-runtime, and the hosted binary to lightspeed-runtime. Use the @lightspeed-ai scope across JavaScript workspaces, with the public client named @lightspeed-ai/sdk and the management server named platform-backend.
• Align Node 24.21.0 and Rust 1.99.0 across development, CI, and release pins. Adapt the code to the upgraded libraries, including Temporal SDK 1.0 and SQLx 0.9. Worker roles run their workflows and activities together through the standard SDK constructor; remove the task-type deployment override and experimental constructor.
• Fix stale Git SHA metadata in cached Rust builds and preserve the SDK's locked production dependencies in Configurator packaging. Clear saved development credentials after a successful explicit database reset so the next startup can provision fresh keys.

Validation:

• Full Rust workspace tests: 2,118 passed; the new build-identity regression also passed. Strict workspace Clippy, formatting, generated contracts, and release metadata checks passed.
• Clean npm ci, npm run check:ci, documentation checks, and all 17 CI/release-script tests passed. A PGlite setup timeout during concurrent compilation passed on the unchanged consumer-gate rerun.
• PostgreSQL migration gates, selected Temporal/storage live tests, and paid OpenAI, Anthropic, and DeepSeek tests passed during the upgrade. Ten live tests, including three paid tool-call tests, passed again after simplifying worker construction.
• All four native binaries built and reported the current commit. Isolated SDK, Configurator, backend, and connector package smoke checks passed, including JavaScript Temporal native-core initialization. The final launcher checks cover the reset changes.
• Workflow lint, shell syntax, change classification, and pinned container base manifests were checked. Container images were not built locally; Linux GNU/musl builds and image smoke checks remain for CI/CD.