[Security] Harden URL sanitization

[gonzaloriestra]

Why is this change necessary?

Currently, sanitizeURL redacts some sensitive query parameters but misses several others commonly used in OAuth 2.0 and authentication flows. It also fails to redact passwords in the URL authority (Basic Auth), which are preserved by the URL object.

Internal Consideration

This change hardens a core utility used for logging URLs, ensuring better protection against accidental credential leakage.

Checklist

• I've added a changeset (if applicable)
• I've followed the contributing guidelines
• I've linted and formatted my code
• I've added tests to cover my changes
• I've verified my changes on a real-world app (if applicable)
• I've documented my changes (if applicable)

---

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