Fix/upgrade playwright go v0.6100.0

[danilodeLuca]

Fixes: #1531

Problem
Versions of playwright-go before v0.6100.0 download the Playwright driver from playwright.azureedge.net/builds/driver/..., which Microsoft retired on 2026-07-08. That causes 404s on fresh installs — the same issue reported in antigravity-cli#566.

Changes made
Upgraded dependency from github.com/playwright-community/playwright-go v0.4702.0 → github.com/mxschmitt/playwright-go v0.6100.0

v0.6100.0 assembles the driver from npm (playwright-core) + nodejs.org instead of the deprecated CDN (playwright-go#615)
The module path moved from playwright-community to mxschmitt in this release

Updated imports in:

• pkg/provider/browser/browser.go
• pkg/provider/browser/browser_test.go
• mocks/Page.go, mocks/Request.go, mocks/Response.go

Fixed API break — StorageState() now takes options instead of a plain path string:

browser.go
Lines 139-142
		_, err := context.StorageState(playwright.BrowserContextStorageStateOptions{
			Path: playwright.String(storageStatePath),
		})

Updated README link to the new module location.

[leonidasKap]

lgtm - I 'd recommend a local build and smoke test. Thank you

[danilodeLuca]

@leonidasKap Thanks — did a local build and smoke test on this branch (mxschmitt/playwright-go v0.6100.0):

Build

• go build -o bin/saml2aws ./cmd/saml2aws succeeded
• Binary starts (--version / --help OK)

Tests

• go test ./pkg/provider/browser/... passed

Playwright smoke (CDN fix) Fresh driver dir (no existing cache):

• playwright.Install() succeeded (driver assembled via npm + nodejs.org)
• Headless Chromium launch + page navigation succeeded
• Confirmed the old CDN is still dead (playwright.azureedge.net/builds/driver/... → 404)

Looks good on my side.