electron: allow the redirect from voice.google.com/about so WAA can init

[jacobjeger]

The problem

voice.google.com/about now redirects to workspace.google.com/products/voice/, which is not in staticAllowedURLs. onBeforeRequest therefore cancels the window's own navigation:

electron: Failed to load URL: https://workspace.google.com/products/voice/
          with error: ERR_BLOCKED_BY_CLIENT

loadURL rejects, so waiting_for_init is never printed and inited stays false. Every later signature request then takes the init branch in processIPC and fails:

[WARN] Timed out waiting for signature ... error="request timed out"
[WARN] Received error ... error="invalid init data"
[ERRO] Failed to generate signature ... error="invalid init data"

Messages still send, but with no WAA signature at all, which is the documented path to HTTP 429.

Why this is easy to miss

Electron launches and logs normally — it just never finishes init. From the outside it looks like a working setup. This may explain #4, #7 and #9, where people installed Electron and still saw 429s (including electron status: ok).

The fix

Allow top-level navigations anywhere under google.com, so a future redirect change cannot break init again. Sub-resources stay restricted to the WAA script alone, as before.

A narrower fix would be adding the single new URL to staticAllowedURLs — happy to switch to that if you would rather keep the allowlist strict. The diagnosis matters more than my particular patch.

Verification

Deployed on a self-hosted bridge. Before: ERR_BLOCKED_BY_CLIENT then invalid init data on every send. After: Waa ping successful, and no invalid init data or ERR_BLOCKED_BY_CLIENT since.