⚡ Bolt: Optimize orbital pass prediction loop by skipping hidden points

[d3mocide]

💡 What: Moved point dictionary creation (with its strftime formatting and rounding) inside the el >= min_elevation condition in get_passes. Added a learning to .jules/bolt.md.
🎯 Why: The orbital pass predictor runs an 8640-iteration loop for a 24-hour window at 10s steps for each satellite. Formatting timestamps and creating dictionaries for points that are below the horizon (which is the vast majority) caused high CPU usage.
📊 Impact: Reduces processing time for orbital pass prediction by ~8-10x per satellite by deferring string formatting until a visible pass is detected.
🔬 Measurement: Running a simulated loop showed execution dropping from ~0.70s to ~0.08s for a single satellite. Can be verified by using /api/orbital/passes with heavy categories like GPS or Weather.

---

PR created automatically by Jules for task 16407384215209545323 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.