⚡ Bolt: Optimize numeric bounds checking

[ManupaKDU]

💡 What: Refactored separate numeric bounds checks (e.g., ip < 0 or ip > MAX) into combined short-circuiting chains (e.g., not (0 <= ip <= MAX)).
🎯 Why: To marginally improve fast-path execution speed and code readability by avoiding redundant evaluations.
📊 Impact: Micro-optimization providing slightly faster execution speed at the bytecode level by evaluating the middle expression only once.
🔬 Measurement: Run python3 -m unittest test_testping1.py to ensure bounds checks still function correctly.

---

PR created automatically by Jules for task 14703970827361765212 started by @ManupaKDU

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