feat(kiloclaw): add bot identity onboarding

[RSO]

Summary

• add a new bot identity onboarding step before permissions so new KiloClaw instances can capture name, nature, vibe, and emoji during setup
• persist bot identity through the frontend, tRPC, platform API, durable object state, and gateway/controller pipeline so the values survive restarts and can be applied live
• generate workspace/SOUL.md from the saved identity on boot and live updates, while removing legacy workspace/BOOTSTRAP.md and workspace/IDENTITY.md files

Verification

• pnpm typecheck (repo root) — passed
• pnpm typecheck (kiloclaw/) — passed
• pnpm exec vitest run controller/src/bootstrap.test.ts controller/src/routes/files.test.ts (kiloclaw/) — passed

Visual Changes

Before	After
Onboarding began at the permissions step with no bot identity capture.	Onboarding now starts with a dedicated bot identity step before permissions, then writes the configured identity into workspace/SOUL.md.

Reviewer Notes

• The main cross-cutting change is the new patchBotIdentity flow, which needs to stay in sync across the personal router, org router, platform route, DO method, and controller endpoint.
• SOUL.md is now the canonical identity file; both boot-time and live writes remove legacy BOOTSTRAP.md and IDENTITY.md files when present.