feat: cache notifications in IndexedDB via storageManager

[gushishang]

Motivation

• Notification payloads are effectively immutable and can be large, so persisting them in IndexedDB improves durability and performance without changing the API contract.
• The goal is to keep all storage access behind the app's storage middleware instead of using browser APIs directly.

Description

• Extended localStorages with notificationsCache and added IndexedDB helpers openIDB, idbGet, and idbSet to src/services/storage/index.ts.
• Exposed middleware-level methods getObjFromIDB and setObjToIDB on storageManager to read/write structured entries via IndexedDB.
• Updated src/components/messages/NotificationList.vue to restore cached notifications on startup using the cache key notifications:${CategoryID}:${locale.value}, merge fetched pages with existing items, deduplicate by ID, and persist merged results to IndexedDB.

Testing

• Ran a full production build with npm run build (includes vue-tsc type check) and the build completed successfully.
• Verified the application rebuilt with only the intended files changed and no build-time errors were produced.

---

Codex Task

[wsxiaolin]

@codex

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[gushishang]

@codex

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3d61ee5154

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Include user identity in notification cache key

The new cache key only uses CategoryID and locale, so cached notifications are shared across accounts on the same browser profile. On a logout/login switch, restoreNotificationsFromCache() will hydrate another user's messages before any API response arrives, which is a privacy leak and can also leave the list offset (skip) inconsistent for the new account. Add a stable per-user identifier to the key (or clear this store on auth change) to keep notification data isolated.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Reset offset when refreshing after restoring cached items

Setting skip to cached.value.length causes offset pagination to miss newly arrived notifications. If new messages were inserted at the top since the cache was written, the next /Messages/GetMessages call (which uses Skip: skip.value) skips over those unseen entries, so users can miss fresh notifications indefinitely. After restoring cache, refresh should fetch from the head (or use a cursor/anchor) instead of reusing list length as an offset.

Useful? React with 👍 / 👎.