fix: request name reverts after renaming an open request panel (#24)

## Description

### Problem
If a request panel is open and you rename that request from the sidebar,
sending (or saving) the request afterward silently restores the old
name.

### Root cause
`SidebarProvider.renameRequest` persists the new name to storage and
updates the panel title via `RequestEditorProvider.updatePanelTitle`,
but never notifies the already-open webview. The webview's React state
keeps the stale name in its `config` object. Both "Send Request" and
"Save" post that full `config` back to the extension host, which writes
it straight to storage and the sidebar tree — so the stale name
overwrites the rename.

### Fix
`updatePanelTitle` now also posts a `requestRenamed` message to the
webview. `RequestContext.tsx` handles it by updating `config.name` in
state, keeping the webview in sync so subsequent saves carry the correct
name.

### Files changed
- `src/providers/RequestEditorProvider.ts`
- `src/webview/request/RequestContext.tsx`

## Test plan
- [x] `npx tsc --noEmit` passes
- [ ] Manual: open a request, rename it via the sidebar context menu,
then click Send — confirm the name stays renamed in both the sidebar and
the panel title
- [ ] Manual: rename, then click Save — confirm the name persists after
reopening the panel

Author: slverma

src/providers/RequestEditorProvider.ts

@@ -49,6 +49,9 @@ export class RequestEditorProvider {
     const panel = RequestEditorProvider.openPanels.get(requestId);
     if (panel) {
       panel.title = newTitle;
+      // Sync the webview's in-memory config so a subsequent save (e.g. from
+      // Send Request) doesn't post back the stale name and undo the rename.
+      panel.webview.postMessage({ type: "requestRenamed", name: newTitle });
     }
   }
 

src/webview/request/RequestContext.tsx

@@ -340,6 +340,9 @@ export const RequestContextProvider: React.FC<RequestContextProviderProps> = ({
         case "historyUpdated":
           setHistoryEntries(message.entries || []);
           break;
+        case "requestRenamed":
+          setConfig((prev) => ({ ...prev, name: message.name }));
+          break;
         case "historyRestored":
           setConfig((prev) => ({
             ...prev,