Fix PopupActions calling StorageHelper directly instead of via background messaging

[Copilot]

StorageHelper is intended to be background-script-only, but PopupActions.deleteWorkspace, renameWorkspace, and clearWorkspaceData were calling StorageHelper.getWorkspaces() directly from the popup context after their respective operations.

Changes

• popup-actions.ts: Replace direct StorageHelper.getWorkspaces() calls with getWorkspaceStorage() in deleteWorkspace, renameWorkspace, and clearWorkspaceData

getWorkspaceStorage() (from popup.js) fetches workspaces from the background script via chrome.runtime.sendMessage, which is the correct pattern already used by openWorkspace and handleNewWorkspaceResponse.

// Before
WorkspaceEntryLogic.listWorkspaces(await StorageHelper.getWorkspaces(), await Utils.getAllWindowIds());

// After
WorkspaceEntryLogic.listWorkspaces(await getWorkspaceStorage(), await Utils.getAllWindowIds());

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• edgedl.me.gvt1.com
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node install.mjs (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)