⚡ Bolt: [Performance] Batch Telegram broadcasts concurrently

[miclaldogan]

💡 What: Replaced sequential HTTP post calls for Telegram broadcast in maintenance and reflection workflows with concurrent execution using asyncio.gather.
🎯 Why: Iterating over a list of users to sequentially send network requests creates an N+1 API latency bottleneck, causing the workflows to wait idly.
📊 Impact: Eliminates sequential network latency. Sending messages to N users now takes roughly the time of 1 request.
🔬 Measurement: Verify by executing the test suite or broadcasting to multiple telegram users.

---

PR created automatically by Jules for task 1626051811597528370 started by @miclaldogan

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