⚡ Bolt: O(log n) market data lookups

[toreleon]

💡 What:
Replaced Array.prototype.filter() with a custom binary search function (findLastBarIndex) for locating specific timestamps in strictly chronologically sorted array data structures, primarily impacting OHLVC lookups inside backtestRunner.ts and clipBars.

🎯 Why:
During historical backtesting, runBacktestSession frequently performs lookups against arrays containing thousands of bars across various securities and indexes to establish values for standard calculations like vnindexAt or priceOverride. Previously, the engine used array.filter(b => b.time <= asOf), which scans the entire array on every request resulting in O(N) operations and heavy continuous array allocations resulting in measurable slowdowns.

📊 Impact:

• Search execution time drops from O(N) linear time scanning down to O(log N).
• Array allocation and copying (O(N)) are completely eliminated from the inner loop, bypassing the garbage collector and freeing up significant processing overhead.
• Backtesting performance execution experiences a quantifiable boost.

🔬 Measurement:
Run any extensive historical backtest execution containing numerous intervals using pnpm test or via standard client execution paths. The speed enhancement should be noticeable in comparison to prior builds.

---

PR created automatically by Jules for task 518257244276759100 started by @toreleon

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