perf: Use only one ps exec to find a Chromium browser opened on Mac OS

[ArnaudBarre]

Description

See #10485 (comment)

Additional context

After a quick benchmark I saw that adding a grep was not making things faster

Script

import { execSync } from "node:child_process";

const supportedChromiumBrowsers = [
  "Google Chrome Canary",
  "Google Chrome Dev",
  "Google Chrome Beta",
  "Google Chrome",
  "Microsoft Edge",
  "Brave Browser",
  "Vivaldi",
  "Chromium",
];

const start = performance.now();
for (let i = 0; i < 100; i++) {
  const ps = execSync("ps cax").toString();
  const browser = supportedChromiumBrowsers.find((b) => ps.includes(b));
}
console.log(`no grep: ${(performance.now() - start).toFixed(2)}ms`);

const start2 = performance.now();
for (let i = 0; i < 100; i++) {
  const ps = execSync(
    `ps cax | grep "${supportedChromiumBrowsers.join("\\|")}"`,
  ).toString();
  const browser = supportedChromiumBrowsers.find((b) => ps.includes(b));
}
console.log(`grep: ${(performance.now() - start2).toFixed(2)}ms`);

Also the tab is now reused is the request browser is chromium based

[ArnaudBarre]

If the node16 test known to be flacky or is it a regression?

[patak-dev]

It is a flaky test, it got a lost worse in the past week