⚡ Bolt: [performance improvement] Defer allocations in orbital pass loop

[d3mocide]

💡 What: Moved the point dictionary allocation (which includes an expensive strftime and two round calls) inside the if el >= min_elevation: visibility check in backend/api/routers/orbital.py.
🎯 Why: In the high-frequency orbital pass prediction loop, satellite positions are often below the minimum elevation threshold. Calculating formatted strings and allocating dictionaries for these non-visible points wastes CPU cycles and memory.
📊 Impact: Significantly reduces string formatting and memory allocation overhead during orbital pass prediction, leading to lower CPU usage and faster response times, especially when querying large constellations.
🔬 Measurement: Verified by running the backend test suite (pytest tests/) and ensuring linting (ruff) and static typing (mypy) continue to pass without regressions.

---

PR created automatically by Jules for task 7338790535840380967 started by @d3mocide

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