Switch to new Chrome headless mode

[colinrotherham]

What

We're getting lots of warnings about Chrome { headless: true } related to the new headless mode in v112

Chrome’s Headless mode gets an upgrade: introducing --headless=new
https://developer.chrome.com/articles/new-headless/

We should investigate and switch to { headless: 'new' } unless we hit issues:

Technically, the old Headless was a separate, alternate browser implementation that happened to be shipped as part of the same Chrome binary. It doesn’t share any of the Chrome browser code in //chrome.

Why

It's important that we

• Test using the same Chrome browser as our users
• Identify Chrome issues early before new headless mode is the default

Who needs to work on this

Developers

Who needs to review this

Developers

Done when

• Switch to new Chrome headless mode

[colinrotherham]

Can confirm it's rather noisy 🤦‍♂️ since we merged:

• Bump puppeteer from 19.9.0 to 19.11.0 #3537

Puppeteer old Headless deprecation warning:
    In the near feature `headless: true` will default to the new Headless mode
    for Chrome instead of the old Headless implementation. For more
    information, please see [https://developer.chrome.com/articles/new-headless/.](https://developer.chrome.com/articles/new-headless/)
    Consider opting in early by passing `headless: "new"` to `puppeteer.launch()`
    If you encounter any bugs, please report them to https://github.com/puppeteer/puppeteer/issues/new/choose.