Redesign the hijack by using layer5 proxy

[ysmood]

As long as we don't use any Devtools API to do it we can make it more flexible and feature-rich.

It will resolve #185 and #61

To enable the TLS hijacking, we can use https://pkg.go.dev/github.com/go-rod/rod#Browser.IgnoreCertErrors

Related issues:

• This is the main blocker: https://bugs.chromium.org/p/chromium/issues/detail?id=1090797
• Proxy for page puppeteer/puppeteer#678

[polyma]

+1.

HTTP CONNECT requests cannot have any of their properties modified by Chromium right now. If you are using a HTTP proxy (https://chromium.googlesource.com/chromium/src/+/HEAD/net/docs/proxy.md#http-proxy-scheme) then page.MustSetUserAgent() will do nothing on the CONNECT request. This is because Chromium doesn't allow you to modify those headers. The result will be a User-Agent like Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/90.0.4403.0 Safari/537.36, which defeats the point of user agent spoofing.

Also relevant:
https://bugs.chromium.org/p/chromium/issues/detail?id=129572