Update Playwright MCP upstream to v0.0.83

Summary

A newer upstream Playwright MCP release is available.

Component	Current	Latest	Update needed
npm `@playwright/mcp`	`0.0.82`	`0.0.83`	yes
Docker `mcr.microsoft.com/playwright/mcp`	`v0.0.82`	`v0.0.83`	yes

Update @playwright/mcp in package.json and package-lock.json.
Update mcr.microsoft.com/playwright/mcp references in Dockerfile, workflows, docs, and parity scripts.
Run npm run check, npm run docker:build, npm run docker:smoke, and npm run bridge:compare.
Update the version compatibility table in README and documentation.

browser_find takes filename to save matches to a file instead of the response (microsoft/playwright#42077). (microsoft/playwright#42968)
browser_navigate and browser_reload report a dialog opened during page load instead of timing out (microsoft/playwright#42817). (microsoft/playwright#42908)
The server no longer crashes when the browser is closed during a download (microsoft/playwright#42831). (microsoft/playwright#42922)
browser_wait_for reports when time is capped at 30 seconds (#1767). (microsoft/playwright#42932)
WebMCP tools no longer stay bound to a stale tab or frame (microsoft/playwright#42816). (microsoft/playwright#42821)
WebMCP tool calls work with Chromium 155+. (microsoft/playwright#42915)
Snapshots quote accessible names that look like regexes, e.g. "/home/" (microsoft/playwright#42807). (microsoft/playwright#42811)
The Docker image reaps orphaned browser processes (#1769). (#1771)

This issue was created automatically by the Playwright MCP upstream monitor workflow.