🛡️ Sentinel: [CRITICAL] Fix database credential exposure in chat history

[keough99]

🚨 Severity: CRITICAL
💡 Vulnerability: The [p]levelerdb setup command accepted MySQL database credentials (including the password) as plaintext arguments. Because it didn't restrict execution to Direct Messages, these credentials could be exposed in a public server's message history if an admin ran the command incorrectly.
🎯 Impact: An attacker could scrape or view the server's message history to obtain the MySQL database credentials, leading to a complete compromise of the database and its user data.
🔧 Fix: Added a ctx.guild check to levelerdb_setup. If executed in a public channel, it gracefully handles deletion of the message (masking HTTPException if permissions lack) and directs the user to rerun the command securely in Direct Messages.
✅ Verification: Verified syntax using py_compile and tested database logic in leveler/test_db.py. Checked against standard Discord API boundaries.

---

PR created automatically by Jules for task 7655948427908853368 started by @keough99

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