⚡ Bolt: Batch local keys fetch in PoolController

[zaydiscold]

💡 What: The optimization replaces an N+1 database lookup for getLocalKeys inside PoolController.js's getPoolData accounts loop with a single grouped database query (getAllLocalKeysForUser) before the loop.
🎯 Why: Iterating over accounts and calling store.getLocalKeys inside Promise.allSettled triggers a separate database query per account.
📊 Impact: Reduces O(N) database queries to a single query + O(N) Map lookups, vastly accelerating pool manager page load for users with multiple accounts.
🔬 Measurement: Ensure accurate functionality. Validate pool stats render matching total amount of keys added across multiple accounts. Compare SQLite query logs before and after patch.

---

PR created automatically by Jules for task 13531025740241254125 started by @zaydiscold

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[zaydiscold]

Closing as a duplicate of #65, which is now merged. #65 batches only the accounts being rendered and keeps grouping in the store layer, avoiding unnecessary user-wide key loading.

[google-labs-jules]

Closing as a duplicate of #65, which is now merged. #65 batches only the accounts being rendered and keeps grouping in the store layer, avoiding unnecessary user-wide key loading.

Understood. Acknowledging that this work is now obsolete as an alternative solution (#65) has been merged.