[Hug0-Drelon]

What?

• Add wpCliCommand option to getPlaywrightConfig() for wp-env 11+ setups using .wp-env.test.json
• Add shared runWpCli() and getWpCliCommand() helpers for running WP-CLI commands in the test environment
• Update createTranslator() to use the configurable command instead of a hardcoded tests-cli container
• Fix getPlaywrightConfig() so spreading remaining Playwright options no longer overwrites merged use and webServer defaults
• Document wpCliCommand, runWpCli, and getWpCliCommand() in README

Why?

wp-env 11+ deprecates the built-in tests-cli container in favor of separate config files (e.g. .wp-env.test.json with run cli). Consumer projects were duplicating runWpCli helpers and createTranslator was failing against the new setup.

How?

• getPlaywrightConfig({ wpCliCommand }) sets WP_ENV_CLI_COMMAND at config load time
• getWpCliCommand() resolves the base command from WP_ENV_CLI_COMMAND or falls back to npx wp-env run tests-cli
• runWpCli(command, shellPrefix?) runs WP-CLI via the resolved command
• setWpCliCommand() remains internal to the package (not publicly exported)
• use, webServer, and wpCliCommand are destructured out of options before spreading remaining Playwright options

Test plan

• npm run build passes
• npm run lint:js passes
• Consumer project configures wpCliCommand: 'npx wp-env --config=.wp-env.test.json run cli' and createTranslator() succeeds
• Consumer project can replace local runWpCli helper with the package export