fix: use bunx instead of npx to read Playwright versions under Bun

[mirao]

Closes #5713

Problem

getPlaywrightBrowsers() in lib/command/info.js hardcoded the Node package runner:

const info = execSync('npx playwright install --dry-run').toString().trim()

A Bun-only environment has no npx on PATH, so execSync throws and the catch reports Playwright not installed on an install where Playwright and its browsers are present. It is a false negative rather than a visible error, so it reads as a genuine misconfiguration.

Fix

Pick the package runner from the runtime that is actually executing rather than from whatever PATH holds, via process.versions.bun — the same detection already used by getRuntimeInfo() in #5700.

function getPackageRunner() {
  if (process.versions.bun) return 'bunx'
  return 'npx'
}

bunx playwright install --dry-run resolves the local node_modules/.bin/playwright and emits output identical to the npx form, so parsePlaywrightBrowsers() needs no change and Node behaviour is unchanged.

This is the only place CodeceptJS actually shells out to npx; every other occurrence under lib/ is documentation text. It removes the need to symlink npx to bun in Bun images.

Verification

codecept info with npx absent from PATH entirely, before and after:

# before
$ PATH=/path/to/bun/bin:/usr/bin:/bin bun ./bin/codecept.js info <dir>
  bunInfo:  1.4.2
  playwrightBrowsers:  "Playwright not installed"

# after
  bunInfo:  1.4.2
  playwrightBrowsers:  "chromium: 148.0.7778.96, firefox: 150.0.2, webkit: 26.4"

Node is byte-identical to before the change:

  nodeInfo:  24.18.0
  playwrightBrowsers:  "chromium: 148.0.7778.96, firefox: 150.0.2, webkit: 26.4"

Unit tests cover both branches of the detection; test/unit/command/*.js passes.

🤖 Generated with Claude Code