⚡ Bolt: [performance improvement] Add in-memory cache to SearchTool

[thirdbase1]

💡 What: Added an in-memory Map cache to SearchTool.deep within the execution wrapper.
🎯 Why: Agentic loops frequently query the same context multiple times (e.g., during planning and then execution). This causes significant performance bottlenecks by issuing identical, expensive external queries.
📊 Impact: Eliminates redundant network operations and latency, providing instant (O(1)) responses for repeated queries during an agentic session.
🔬 Measurement: Verified by reviewing CoreEngine logs confirming Cache hit for deep search: messages instead of subsequent Initiating deep search for: log entries for the same query. Tests (npm run test) continue to pass confirming no regressions.

---

PR created automatically by Jules for task 4573425915460445573 started by @thirdbase1

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