🔒 Fix sensitive data exposure in users.php

[tsainez]

🎯 What: The users.php page previously dumped raw database result arrays straight to the page via var_dump().
⚠️ Risk: This vulnerability leaked sensitive user information directly into the UI, including database keys and sensitive fields such as passwords or password hashes. It also presented a risk of XSS since data wasn't escaped.
🛡️ Solution: The var_dump was removed and replaced with a dynamic list rendering loop. The loop uses a blacklist approach to explicitly skip rendering any field keys containing "password". Additionally, all outputs are escaped using htmlspecialchars to prevent Cross-Site Scripting (XSS).

---

PR created automatically by Jules for task 17284373868665070333 started by @tsainez

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