Support for new Chromium 112 --headless=new flag, graphics stack enable/disable, lots of docs updates

[Sparticuz]

Breaking changes:
Change to new headless version
Refactor default args, adding many that are default in puppeteer

Non-breaking changes:
Remove node version check and pull regex out into it's own function, fixes #75
Add ability to disable the graphics stack
Add docs on running headfully and running on arm
fixes #63
fixes #69
fixes #38
fixes #55
fixes #42
fixes #28
😃😃😃😃😃😃😃😃😃
More docs, fixes #77

Two new options are available

// True will be the 'old' headless mode, "new" is the new headless mode. "new" is the default
chromium.setHeadlessMode = true | "new";
// true will enable swiftshader and webgl, false disables it. true is the default
chromium.setGraphicsMode = true | false;

These need to be set before launching puppeteer

[arnulfojr]

My understanding is that in serverless environments we need to use swiftshader to use CPU only but we are now introducing a new configuration mode which would can disable webgl.

Would it make sense here to have the mode to have type of "swiftshader" | "swiftshader-webgl" | "webgl-disabled"?

the new option would be to use swiftshader to render webgl content, or ultimately disable webgl completely.

If the intention is to have an actual boolean maybe we can use something like graphicsStackEnabled?

[Sparticuz]

I think for most users, swiftshader can be disabled and not used at all, it saves at least a full second on my testing for initial extracts. Swiftshader/angle is what powers webgl, so I'm not sure what the difference would be for swiftshader or swiftshader-webgl (Maybe my comment was confusing about the swiftshader driver)

[Sparticuz]

Thanks for the comments!