🛡️ Sentinel: [CRITICAL] Fix internal error information leakage

[DerUntote]

🚨 Severity: CRITICAL
💡 Vulnerability: Internal RPC errors (like bitcoind-rpc connection issues) were being directly sent to users in Discord via message.reply(err.message). This leaks system internals, database details, and backend connection details, potentially exposing attack surface.
🎯 Impact: Attackers could gain insights into the system's infrastructure and error handling mechanisms to craft further attacks.
🔧 Fix: Replaced message.reply(err.message) with a generic, sanitized error message ("An error occurred while processing your request."). Internal errors are now securely logged via console.error(err) for developers. Added a .catch() handler for message deletion to prevent unhandled promise rejections on already-deleted messages. Applied across all Tipper.js modules.
✅ Verification: Ran syntax validation (node -c) on all modified *Tipper.js modules to ensure no regression was introduced. Verified via code review.

---

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