feat!: switch to Chrome for Testing instead of Chromium

[OrKoN]

Puppeteer switches to Chrome for Testing binaries by default. These binaries will be more similar to Chrome binaries than Chromium binaries in the future. Since the binary is different we mark the change as breaking and include a few other breaking changes related to how the browsers are installed:

• rolls Chrome for Testing 112.0.5615.121 (see https://goo.gle/chrome-for-testing).
• removes BrowserFetcher that can only deal with Chromium builds in favor of @puppeteer/browsers.
• enables mac-arm64 builds to be available for download (previously experimental).
• removes ToT CI for now since we don't use it so much and we need to find a new way to test with an arbitrary version.
• removes PUPPETEER_SKIP_CHROMIUM_DOWNLOAD in favor of PUPPETEER_SKIP_DOWNLOAD since the flag always affected any browser, not only Chromium.
• removes PUPPETEER_CHROMIUM_REVISION in favour of PUPPETEER_BROWSER_REVISION since the flag always affected any browser, not only Chromium.
• removes the fallback to /usr/bin/chromium-browser on non-mac-arm64 platforms. Please define the executable path explicitly.
• removes the bisect script in favor of using browser-specific bisect tools.
• removes compatibility DOWNLOAD_HOST rewrites for chromium-browser-snapshots. PUPPETEER_DOWNLOAD_HOST now works as a base URL.

[mathiasbynens]

Thanks for the clear summary in the PR description, and for making the changes in the first place! Nice work.

[OrKoN]

Trying a different CfT version to see if PDF on Windows still has issues. Do not land please.

[OrKoN]

@kblok where do you see that? we renamed from Chromium to browser in many places, so exactly the opposite.

[kblok]

@OrKoN oh, sorry. My bad. Removing the comment to avoid confusion. Thank you!

[drmrbrewer]

@OrKoN I'm currently installing the chromium package in my Debian environment to get the chromium binary needed for puppeteer. The reason I'm installing it myself, rather than relying on the binary bundled with puppeteer, is because puppeteer doesn't provide one for arm64.

It doesn't seem like there's a "chrome for testing" package for Debian, or even a "chrome" package. Can we continue to use the chromium binary? Or any thoughts on how I would go about installing the relevant "chrome for testing" binary on Debian?

[OrKoN]

@drmrbrewer you can use Chromium, but we won't test with Chromium builds anymore. We are working on getting arm64 for Chrome for Testing but I cannot give an estimate.

[drmrbrewer]

@OrKoN OK thanks. That linked issue for arm64 has been open for 18 months now, and has collected over 70 thumbs-up votes, so it seems like there is a need... and this move to "chrome for testing" makes it even more pressing now, because it is now apparently even more difficult to install the right binary on arm64... I doubt that the Debian package library will add a "chrome for testing" cross-platform package because it is much more niche than chromium (according to my understanding).