🛡️ Sentinel: [MEDIUM] Prevent internal RPC error leakage

[DerUntote]

🚨 Severity: MEDIUM
💡 Vulnerability: Internal RPC errors were being returned directly to users via message.reply(err.message), which could leak sensitive internal system information, file paths, or connection issues in production.
🎯 Impact: Exposing raw error messages could provide attackers with detailed information about the bot's internal workings and connectivity. Also, unhandled promise rejections on the .then() chain of Discord messages could lead to unexpected bot crashes.
🔧 Fix: Replaced direct err.message user feedback with a sanitized, generic error string: 'An internal error occurred while processing your request.' while internally logging the actual error via console.error(err) for debugging purposes. Appended .catch(console.error) to message.reply().then() promises to safely handle rejections.
✅ Verification: Verified via manual syntax checks with node -c on updated files, format checks with npm run precommit, and git diff that no .reply(err.message) occurrences remain in the bot/modules/*Tipper.js structure.

---

PR created automatically by Jules for task 3933508692704994974 started by @DerUntote

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