🎨 Palette: Disable input during offline state

[teerthsharma]

💡 What

Updated the ChatInterface to dynamically disable the message input and submit button when the connection to the DSP Bus/kernel is offline (tunnelStatus !== 'LOCKED').

🎯 Why

Previously, if the tunnel was offline, users could still attempt to interact with the input field, which led to confusion and ghost interactions since messages couldn't actually be sent. This change provides immediate, clear feedback regarding the system's connection state.

📸 Before/After

Before: Input was active and read "Inject knowledge into the kernel..." even when offline.
After: Input is disabled with reduced opacity, showing a "not-allowed" cursor, and reads "Reconnecting to kernel...".

♿ Accessibility

• Added dynamic aria-labels on the send button indicating the waiting state.
• Added dynamic title tooltips for hover contexts.
• Leveraged native disabled HTML attributes and distinct visual cues via Tailwind (disabled:opacity-50 disabled:cursor-not-allowed) to convey state clearly to all users, including those using screen readers.

---

PR created automatically by Jules for task 80340966577928571 started by @teerthsharma

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