feat(data): add note metadata DataApi and cache schemas for v2 migration

[DeJeune]

What this PR does

Before this PR:
Note starred paths were stored in Redux (store/note.ts) with no database persistence. UI state like active file path and expanded paths had no v2 data layer support.

After this PR:

• Adds a note SQLite table for note metadata (path, isStarred, timestamps), extensible for future fields (AI tags, etc.)
• Adds DataApi endpoints (GET /notes, GET/PATCH/DELETE /notes/:path) with NoteService
• Adds PersistCache keys (notes.active_file_path, notes.expanded_paths) for UI state
• Preference keys for note settings were already mapped in a previous PR

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

This is the data API layer (Phase 2) for migrating store/note.ts to the v2 architecture. The note table uses file path as primary key since notes are filesystem-based. It is designed to be extensible — isStarred is the first metadata field, with future fields (AI features, tags) planned under the same table.

The following tradeoffs were made:

• Used path as primary key instead of UUID — notes are identified by filesystem path, making path the natural key
• getByPath auto-creates metadata entries (upsert) — avoids requiring explicit creation before use

The following alternatives were considered:

• A separate note_starred table with only path+createdAt — rejected because the notes domain will grow with more metadata fields

Breaking changes

None.

Special notes for your reviewer

• This PR only covers the data API layer (DB schema, service, handler, cache schemas). Renderer-side migration (replacing Redux hooks) will be a follow-up PR.
• The 10 preference keys for note settings were already defined in preferenceSchemas.ts and PreferencesMappings.ts in a previous commit.

Checklist

• 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 refactoring
• Self-review: I have reviewed my own code before requesting review from others

Release note

NONE

[DeJeune]

Note

This issue/comment/review was translated by Claude.

Need to consider the collaboration with #12557

---

Original Content

需要考虑到 #12557 的合作

[EurFelux]

Also #12150