⚡ Bolt: [performance improvement] Optimize list rendering with React.memo in Panels

[primoscope]

💡 What: Extracted the list items in ProgressPanel.tsx and LogPanel.tsx into isolated React.memo components.

• In ProgressPanel, DownloadItem now uses a custom equality function to ensure it only re-renders when visual data changes, preventing unnecessary renders on high-frequency API polling or WebSocket updates.
• In LogPanel, LogItem now relies on a stable client-generated ID for React keys (instead of array indices) to ensure optimal reconciliation when logs are appended.
• Moved static formatting and coloring helper functions outside the component bodies to prevent reallocation on every render cycle.

🎯 Why: As the application handles high-frequency WebSocket events (progress updates and logs), rendering the entire array loop on every update is a significant O(N) performance bottleneck. React.memo ensures only the specific item being updated re-renders. Additionally, using array indices as keys in React can cause unpredictable behavior and performance degradation when list contents change.

📊 Impact: Expected to drastically reduce React reconciliation times and prevent CPU spikes when multiple downloads are active and emitting frequent progress/log events. List re-renders are now O(1) for updates instead of O(N).

🔬 Measurement:

1. Start multiple concurrent downloads.
2. Open React DevTools Profiler and record interactions.
3. Observe that only the individual DownloadItem or LogItem components re-render when a WebSocket message is received, rather than the entire ProgressPanel or LogPanel component.

---

PR created automatically by Jules for task 2521116736148266716 started by @dzp5103

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