feat(studio): complete MPA provisioning and safe resource deletion

[moidream]

Summary

Studio now keeps general-agent deployment separate from MPA lifecycle operations and completes the managed MPA resource flow. General deployments retain their original build/deploy/publish/configuration stages and no longer apply MPA Profiles or appear in the MPA filter without explicit MPA intent.

• Prepare one dedicated business PostgreSQL Workspace per new MPA, with an aidb database and a searchable Runtime-name-based Workspace name. Preserve existing shared bindings and submitted request identities. Check Runtime, sandbox-template, Workspace and active-task name collisions before accepting a new request; show conflicts in a red alert.
• Automatically prepare an enterprise OpenViking collection for new Volcengine Beijing requests, wait for readiness and inject the four connection variables server-side. Pin nonsecret ownership/bindings for retries; keep API keys out of browser drafts and task storage. BytePlus and legacy manual requests retain their existing flow.
• Delete an MPA without requiring a Runtime Profile. Check active sessions and verified ownership, remove its exclusive sandbox template and Skill Space, then delete Runtime. Retain databases, OpenViking and shared resources. Recover timed-out responses by checking actual deletion status instead of silently reporting success.
• Add editable maximum instances in basic information, defaulting to 20. Persist the selected number and pass it to Runtime MaxInstance; retries retain it, and legacy requests without the field preserve their original configuration.
• Let Runtime choose Feishu group-session defaults by omitting the optional scope from Studio's add-group form. Preserve existing group records and the single-/multi-bot API contracts.

Includes bilingual designs/contracts, regression tests, and rebuilt packaged WebUI assets. The four feature commits are rebased onto the current upstream main; the original fork development branch is preserved.

Validation

• PASS: repository-wide pre-commit (Ruff, formatting, hardcoded-secret and YAML-secret scans). Added the repository-standard Apache headers to six new Python modules/tests; AST comparison confirmed no executable-code changes, and 74 affected tests passed after this comment-only correction.
• PASS: 1,185 affected Python startup/managed-provisioning/Profile-route/RBAC tests after the startup correction.
• PASS: 1,389 Node tests, 95 React tests and production build; 22 sidecar coverage tests (100% lines / 94.44% branches); i18n and 113 packaged files / 350 asset references.
• PASS: Ruff/Pyright for the corrected OV adapter/tests (0 type errors/warnings). Complete lock graph validated with an isolated npm 10.9.2 Linux/x64 npm ci --ignore-scripts --dry-run.
• Earlier full local Python run: 7,184 passed, 2 failed, 53 skipped, 4 xfailed. The startup regression was corrected and passed the affected rerun. The remaining test_success_uses_trusted_scope_and_hashes_utf8_bytes failure also reproduces on unchanged upstream b8038fb1 under Python 3.10/macOS because Markdown MIME resolves to application/octet-stream; the unrelated artifact writer/test is unchanged. The global suite was not repeated after the bounded import/lock correction.
• Browser validation of the new maximum/duplicate-name UI used real Chromium with simulated APIs, covering normal, invalid input, navigation, read-only retry recovery, legacy drafts, BytePlus and narrow layouts. No additional real cloud provisioning or paid OV smoke was run for PR preparation.

New enterprise OpenViking collections use provider billing. Database/OV/shared resources are retained on Agent deletion; legacy resource bindings are not migrated. Upstream CI will provide Linux/matrix verification.