[Security] Harden openURL protocol validation

[gonzaloriestra]

Why is this change necessary?

The openURL function was previously passing the input string directly to the open library without validation. This allowed any URL protocol to be handled by the system's default opener, which could lead to security risks if an attacker can influence the URL (e.g., via javascript: or data: protocols).

How to test your changes?

CI

Checklist

• I've added a description of what is changed and why.
• I've added a link to the document or issue it's fixing (if applicable).
• I've added some screenshots/recordings of the before/after (if applicable).
• I've added tests for the new/updated code.
• I've followed the standard guidelines.
• I've used existing components (if applicable).
• I've checked that the changes are backwards compatible (if applicable).
• I've added a changeset (if applicable).

---

PR created automatically by Jules for task 4911786415154034671 started by @gonzaloriestra

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