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

[DerUntote]

🚨 Severity: MEDIUM
💡 Vulnerability: The internal daemon/RPC errors from .sendFrom were being passed directly to discord via message.reply(err.message).
🎯 Impact: This could expose infrastructure details, node info, or other unexpected sensitive information when an internal command fails.
🔧 Fix: Instead of exposing err.message directly in the reply, catch it, log it internally for administrators with console.error(err);, and return a generic user-facing message like 'An internal error occurred.'. Make sure to chain .catch(() => {}) on message.delete(10000) to prevent uncaught exceptions if the message is deleted before 10s.
✅ Verification: Ran git diff, syntax checking node -c, and auto-formatting npx prettier on all touched *Tipper.js files.

---

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