rerefactor(miniapp): Miniapp V2 db schema

[chengcheng84]

What this PR does

Before this PR:
No unified data layer exists for miniapps
After this PR:
Adds the complete v2 foundation for the miniapp management system

Why we need it and why it was done in this way

This is the data layer foundation that Phase 2 (services, handlers, UI) builds on. Splitting into phases keeps PRs reviewable and allows early validation of the schema design.

Breaking changes

None. This is purely additive — new tables, new types, no changes to existing functionality.

Special notes for your reviewer

None

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

• PR: The PR description is expressive enough and will help future contributors
• Code: Write code that humans can understand and Keep it simple
• Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• Documentation: Not required — internal data layer change, no user-facing features
• Self-review: I have reviewed my own code (e.g., via /gh-pr-review, gh pr diff, or GitHub UI) before requesting review from others

Release note

None

[chengcheng84]

@0xfullex I've completed the initial design for the miniapp data layer. Could you please take a look and see if the direction is correct?Thanks

[DeJeune]

Note

This issue/comment/review was translated by Claude.

We also need to migrate the template data and user data.

---

Original Content

还需要迁移一下模板数据和用户数据