fix(qoder): complete Forward resource lifecycle

[heimanba]

Summary

• route Qoder Forward-owned Environments, Skills, Vaults, Files, and Memory Stores through their documented API domains
• allow Forward Templates to reference Environment IDs from either Managed or Forward APIs while creating local Forward Environments only through Forward
• support Forward Template file bindings and explicit/default Memory Store reconciliation
• permanently delete Qoder Memory Stores through the Cloud lifecycle API, including system-managed and stale-mounted Forward Stores

Memory Store lifecycle

• Forward API remains responsible for create, lookup, update, mounts, and Memory content
• permanent Store deletion and failed-create rollback use DELETE /api/v1/cloud/memory_stores/{id}
• default Store metadata and delete_on_destroy cleanup remain resumable through state
• Template archive detaches only project-owned explicit Store mounts

Validation

• SDK unit suite: 631 passed, 0 failed
• post-rebase focused suite: 63 passed, 0 failed
• SDK TypeScript typecheck passed
• changed-file lint and git diff --check passed
• pre-push full workspace verification passed
• live Qoder API validation confirmed Cloud DELETE removes Forward-created, system-managed, and stale-mounted Stores from both API views