Update Puppeteer to version 13.1.1

[Snuffleupagus]

Note in particular https://github.com/puppeteer/puppeteer/releases/tag/v13.1.0 which includes an update to Chromium 98, which adds support for structuredClone in the browser.

[Snuffleupagus]

/botio test

[pdfjsbot]

From: Bot.io (Linux m4)

---

Received

Command cmd_test from @Snuffleupagus received. Current queue size: 0

Live output at: http://54.241.84.105:8877/2314c42a20a388f/output.txt

[pdfjsbot]

From: Bot.io (Windows)

---

Received

Command cmd_test from @Snuffleupagus received. Current queue size: 0

Live output at: http://54.193.163.58:8877/18e8211db619502/output.txt

[pdfjsbot]

From: Bot.io (Linux m4)

---

Failed

Full output at http://54.241.84.105:8877/2314c42a20a388f/output.txt

Total script time: 22.52 mins

• Font tests: Passed
• Unit tests: Passed
• Integration Tests: Passed
• Regression tests: FAILED

  different ref/snapshot: 13
  different first/second rendering: 2

Image differences available at: http://54.241.84.105:8877/2314c42a20a388f/reftest-analyzer.html#web=eq.log

[pdfjsbot]

From: Bot.io (Windows)

---

Failed

Full output at http://54.193.163.58:8877/18e8211db619502/output.txt

Total script time: 60.00 mins

[timvandermeij]

The Chrome on Windows failure here is really weird since it seems to work fine up until a certain point where it starts failing every test with Loading PDF document: Error: Setting up fake worker failed: "Cannot load script at: http://127.0.0.1:60301/build/generic/build/pdf.worker.js". It seems strange to me that it's using a fake worker in the first place?

[Snuffleupagus]

since it seems to work fine up until a certain point

I don't think it actually works all that well since the tests before that run extremely slow.
In any case, any objections to simply going ahead with disabling the affected configuration (since it's unrelated to Firefox) to avoid us becoming "stuck" with dependencies that we cannot update?

[timvandermeij]

Not really. Let's land it as part of #14392 and close this one.