feat: streamline opencode loading screens and reuse the reload flow for vscode Restart API

Loading screens: drop the internal-jargon progress text on the opencode
reload overlay (ConfigUpdateOverlay) and the vscode init splash — show
text only on errors. Replace it with a glow pulse on the OpenCode mark on
the cube's top face; OpenChamberLogo's isAnimated prop was a no-op and now
actually animates. vscode shows the glow on the inline splash logo and the
React app stops writing 'Loading data (… Providers, … Agents)…'.

Restart API: 'OpenChamber: Restart API Connection' now runs the same full
reload flow used after an OpenCode update — the command asks the chat
webview to call reloadOpenCodeConfiguration() (overlay + managed restart
via the bridge + config/data refresh) instead of a bare manager restart,
falling back to the old restart when no webview is open. Mounts
ConfigUpdateOverlay in the vscode app so the overlay actually shows there.

packages/vscode/src/ChatViewProvider.ts

@@ -306,6 +306,23 @@ export class ChatViewProvider implements vscode.WebviewViewProvider {
     });
   }
 
+  /**
+   * Ask the webview to run the full OpenCode reload flow (overlay + managed
+   * restart via the bridge + config/data refresh) — the same flow used after an
+   * OpenCode update. Returns false if no webview is resolved to drive it.
+   */
+  public reloadOpenCode(): boolean {
+    if (!this._view) {
+      return false;
+    }
+
+    this._view.webview.postMessage({
+      type: 'command',
+      command: 'reloadOpenCode',
+    });
+    return true;
+  }
+
   public notifyWindowFocusChanged(focused: boolean): void {
     if (!this._view) {
       return;