⚡ Bolt: Optimize category and profile derivation in CategoryFilterWidget

[alazndy]

🎯 What
Consolidated the previously separate derivations for activeCategories and uniqueProfiles in CategoryFilterWidget.tsx into a single useMemo block utilizing a standard for loop. Added a new entry in .jules/bolt.md documenting the learning.

💡 Why
Previously, generating the activeCategories and uniqueProfiles sets involved multiple passes over the shortcuts array using map and flatMap, creating intermediate arrays before passing them into the Set constructor. For power users with large numbers of shortcuts, this caused unnecessary CPU overhead and garbage collection. Combining them into a single loop avoids intermediate allocations.

📊 Impact
Reduces execution time by ~60% for the derivation logic based on standalone Node.js benchmarks (simulating 10,000 shortcuts, time dropped from ~1771ms to ~681ms for 1000 iterations).

🔬 Measurement
A temporary benchmark.cjs script was created using Node's perf_hooks with a mocked array of 10,000 shortcuts. The unoptimized chained methods and the new consolidated loop were run 1,000 times after warmup, confirming the reduction in execution time. Changes were successfully type-checked via tsc --noEmit and verified via standard Vite build.

---

PR created automatically by Jules for task 8875867067516161800 started by @alazndy

[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.