[microsoft-playwright-automation]

• Roll the driver from 6e2c003f16e01822c3ea45bc894c2542a6e98189 to 20a2087ea43412b90c172c88faef80786ee18b8b.
• Update the README to Chromium 157.0.8103.6 (r1251). The driver includes the updated device user agents, startup network request fixes, and service worker session fix.
• No Python client, API, protocol, or test ports are required. Reporter changes apply only to the upstream JavaScript test runner. Nothing remains to port.
• Checks passed: API comparison, mypy playwright, full Chromium sync and async suites (7,764 passed, 173 skipped, 12 expected failures), and ./scripts/lint.sh.

Upstream commits (4)

• microsoft/playwright@ca7ca3614 fix(chromium): detach page-side service worker session without resuming it (fix(chromium): detach page-side service worker session without resuming it playwright#43566)
• microsoft/playwright@eecb129ca chore: remove onTestPaused from reporters (chore: remove onTestPaused from reporters playwright#43570)
• microsoft/playwright@652f4b0b6 feat(chromium): roll to r1251 (feat(chromium): roll to r1251 playwright#43531)
• microsoft/playwright@20a2087ea fix(chromium): stop remaining startup requests to Google services (fix(chromium): stop remaining startup requests to Google services playwright#43571)

Upstream changes: microsoft/playwright@6e2c003...20a2087

_{Rolled by the roll workflow.}

[Devin Rousso (dcrousso)]

the base and roll both pass the full sync and async suites on Edge 156.0.4314.42, with one retry in RO-170 on the roll and no recurrence of either original Edge timeout

the remaining red checks match screenshot failures and Windows timeout patterns already seen on the base, and the Chromium backend issue in microsoft/playwright#43562 remains separate upstream followup work