⚡ Bolt: [performance improvement] Optimize list filtering with useMemo

[belpythons]

💡 What:

• Added useMemo hooks to cache computationally expensive filtering operations (filteredResources, filteredPosts, and filteredRoadmaps).
• Moved statically defined arrays (like categories, communityLinks, and recentTopics) and helper functions outside of the React component bodies where size constraints allowed.
• Added a new journal entry to .jules/bolt.md.

🎯 Why:
When static arrays or objects are defined inside the component body, they are recreated on every render. Because arrays are compared by reference, not value, they fail referential equality checks, which forces useMemo dependencies to break and triggers unneeded recalculations. By moving these constants outside the component and correctly memoizing the derived derived state, we eliminate unnecessary re-evaluations and re-renders during state updates.

📊 Impact:
Eliminates unnecessary list recalculations during state changes (e.g., when users type into a search input), leading to faster UI updates and reduced CPU overhead.

🔬 Measurement:
To verify, you can monitor the React DevTools Profiler during searches/category changes to confirm that the filter() functions are only invoked when the actual dependency arrays (searchTerm, selectedCategory) change, rather than on every component render.

---

PR created automatically by Jules for task 7798611804299753633 started by @belpythons

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