As can be seen from the first round of testing in PR #15864, trying to update Puppeteer beyond version `19.0.0` completely breaks testing in Firefox. Curiously it does work locally when the `--noChrome` flag is being used, so it seems to be an issue with running tests in both Chrome *and* Firefox in parallel.

We need to fix this, likely by making some adjustments to our test-suite, such that we don't get "stuck" on an older version of Puppeteer without being able to update. (A temporary work-around could also be to disable testing in Chrome.)

const localRevisions = await browserFetcher.localRevisions();
  if (localRevisions.length > 1) {
    for (const localRevision of localRevisions) {
      if (localRevision !== wantedRevision) {
        console.log(`Removing old ${browserName} revision ${localRevision}...`);
        await browserFetcher.remove(localRevision);
      }
    }
  }
  const options = {
    product: browserName,
    headless: false,
    defaultViewport: null,
    ignoreDefaultArgs: ["--disable-extensions"],
  };
  if (!tempDir) {
    tempDir = fs.mkdtempSync(path.join(os.tmpdir(), "pdfjs-"));
  }
  const printFile = path.join(tempDir, "print.pdf");
  if (browserName === "chrome") {
    
    options.args = ["--no-sandbox", "--disable-setuid-sandbox"];
    
    options.args.push("--kiosk-printing");
  }
  if (browserName === "firefox") {
    options.extraPrefsFirefox = {
      
      "dom.disable_beforeunload": true,