pyppeteer: answer proxy auth over CDP Fetch; re-measure the proxy path (v0.1.1)

[jehrr]

• Fix: pyppeteer's page.authenticate needs Network.setRequestInterception, which current Chromium removed. Reproduced here: "'Network.setRequestInterception' wasn't found", and the engine died before its first navigation with any credentialled proxy. The engine now answers Fetch.authRequired itself, giving the credentials only to a Proxy challenge. After the fix: ipify answered through the proxy on 4 of 4 runs.
• Measured: through pyppeteer, the 2Captcha residential exits got the page on 2 of 3 tries, then the listing API refused the exit (its answer carried no CORS permission). No rows, so README and .env.example keep "not measured to work" and now say why.
• Check added: the engine never calls page.authenticate. Controlled: reverting the fix turns exactly that check red.
• Not changed: the Playwright proxy path (6 of 6 resets on the same exits, with the headless shell and full Chromium alike; the cause was not separated).
• Version 0.1.1 and a new CHANGELOG section; the released 0.1.0 section is untouched.

🤖 Generated with Claude Code