🛡️ Sentinel: [HIGH] Fix RPC error information disclosure

[DerUntote]

🚨 Severity: HIGH
💡 Vulnerability: Internal RPC error messages from bitcoind-rpc connections were directly passed to Discord users via message.reply(err.message), potentially exposing sensitive infrastructure details. Additionally, .catch() handlers were missing on the subsequent message.delete() calls.
🎯 Impact: Sending raw daemon error messages to end-users is an information disclosure vulnerability. Missing .catch() handlers on Discord API calls can crash the bot due to unhandled promise rejections.
🔧 Fix: Replaced message.reply(err.message) with console.error(err) and a generic reply message. Appended .catch(() => {}) to message.delete() calls. Added a journal entry to .jules/sentinel.md.
✅ Verification: Ran yarn precommit and node -c on all modified files to verify syntax. Checked that message.reply(err.message) no longer exists in bot/modules.

---

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