Handle foreign extension embeds before debugger attach

[zuogl]

Summary

• add the scripting permission to the Browser Bridge extension
• remove foreign chrome-extension:// iframe/frame/embed/object nodes before attaching the debugger and retry once after a failed attach
• keep the extension manifest regression test aligned with the new permission and include the rebuilt extension bundle

Fixes #661
Refs #249
Refs #652

Why

On some Chrome profiles, opencli twitter search could navigate to a normal https://x.com/... tab but still fail at chrome.debugger.attach() with:

attach failed: Cannot access a chrome-extension:// URL of different extension

I reproduced this locally via the daemon command path. The failure appears when another extension injects a chrome-extension://... embed into the target page, which makes the attach step fail even though the top-level tab URL is debuggable.

Validation

• npm run build in extension/
• npx vitest run src/extension-manifest-regression.test.ts
• manual repro + verification with opencli twitter search "claude code" --filter top --limit 10 -f json after reloading the patched extension