⚡ Optimize processBacklog loop in histogram_storage_sync

[max-ostapenko]

💡 What: Replaced the sequential for...of loop in processBacklog with a concurrent mapLimit approach, using a concurrency limit of 10.
🎯 Why: The sequential iteration was unnecessarily waiting for each BigQuery upload to finish before starting the next. For completely I/O bound tasks like downloading from GCS and uploading to BQ, this severely throttled throughput. The codebase already had a mapLimit utility built for similar concurrency needs.
📊 Measured Improvement: Simulated benchmarking of sequential vs mapLimit(..., 10) demonstrated an ~90% reduction in execution time for the backlog processing loop (from ~5040ms to ~505ms for 50 mocked file operations).

---

PR created automatically by Jules for task 1059346001962473449 started by @max-ostapenko

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