fix: load extensions in recorded tab by using default browser context

[v1s10n-4]

Fixes #890

When --extension is used, record start and window_new now create pages in the default browser context instead of a new isolated context. Chrome extensions only run in the default context; CDP-created contexts are incognito-like and do not load extensions.

[vercel]

@v1s10n-4 is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

[ctate]

Thanks for this fix! The approach is correct — I confirmed the bug by E2E testing on main (extension content script doesn't run in the recorded tab's isolated context) and verified the default-context path works. Two things before merge:

• Run cargo fmt — 4 minor formatting deviations in actions.rs and e2e_tests.rs

• Fix e2e tests: content script isolated world issue — The test extension sets window.__TEST_EXT = true and checks it via evaluate, but content scripts run in Chrome's isolated world — window properties they set are not visible from the main world where Runtime.evaluate runs. The extension should modify the DOM instead (e.g., document.documentElement.setAttribute('data-test-ext', 'true')) and assertions should check document.documentElement.getAttribute('data-test-ext'), since DOM mutations are shared across worlds.

Thank you for the well-scoped contribution and the thorough regression tests!