🛡️ Sentinel: [MEDIUM] Fix log injection in IP scan range setup

[ManupaKDU]

🚨 Severity: MEDIUM
💡 Vulnerability: Log Injection (CRLF). An attacker could pass a malicious string containing newlines (e.g. 192.168.43.1\nERROR: Log injected) to the main execution block. If ValueError was raised, the un-sanitized string was directly formatted into the logging.error() message, allowing the attacker to inject arbitrary entries into the application logs.
🎯 Impact: Log spoofing, tampering with audit trails, and potential exploitation of log aggregation systems.
🔧 Fix: Wrapped the exception message e with repr(str(e)) inside the logging call, which securely escapes control characters (like \n and \r).
✅ Verification: Ran python3 -m unittest test_testping1.py, which includes a newly added test test_main_log_injection to specifically verify the script correctly escapes the log injection vector without breaking existing functionalities.

---

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