MySQL parity with Chat2DB Community

[openai0229]

Baseline

Match the original Chat2DB Community frontend and MySQL behavior at OtterMind/Chat2DB@3cb8af54cad5bd5caa20bb25f10d9b0e4f01931c.

The in-repository acceptance contract is docs/mysql-community-parity.md.

Scope

• Native MySQL object metadata and all original metadata routes (feat(mysql): complete native metadata parity slice #3)
• Full Console query, script, write, transaction, history, cancellation, and large-cell behavior (feat(mysql): complete native Console execution slice #4)
• Table row editing and database/schema/table/view DDL
• Import/export and background task lifecycle
• Datasource lifecycle, SSH, driver management, import/export, and namespaces
• MySQL account administration, routines, structure diff, pins, and ER metadata
• Original SQL parser, formatter, validation, and completion routes
• Original AI workspace plus MySQL Agent, CLI, and MCP conformance
• Real MySQL product tests, Web/Tauri contract tests, complete repository verification, and all CI jobs

Constraints

• Preserve the original Community frontend and styles.
• Use mysql_async for the native MySQL data plane.
• Keep exact Community Java implementations for ANTLR, formatting, completion, and plugin builders where required for behavior parity.
• Do not claim a capability complete until the original frontend route and a real MySQL product test both pass.

[openai0229]

Implemented and merged in #4. The native MySQL Console slice now covers the scoped execution, cancellation, history, and large-value work; remaining broader product parity will be tracked only when separately scoped.

[openai0229]

Closing after PR #4 merge as requested. Broader future parity is intentionally out of scope for this completed issue.