🛡️ Sentinel: [HIGH] Fix sensitive information leakage in RPC error messages

[DerUntote]

🚨 Severity: HIGH
💡 Vulnerability: Internal RPC connection error messages (which may contain internal network or configuration details) were being leaked directly to Discord users via message.reply(err.message).
🎯 Impact: Returning unhandled or raw errors from a backend system to the frontend exposes internal system details to potential attackers.
🔧 Fix: Catch all errors from backend system calls and respond to users with generic error messages while logging the actual err object internally for debugging (e.g. using console.error).
✅ Verification: Verified the file modifications with git diff and syntax with node -c.

---

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