[Bug]: Seems the command options of launchBrowser for Antroid testing does not work

[PupilTong]

Version

main (source code)

Steps to reproduce

https://playwright.dev/docs/api/class-androiddevice#android-device-launch-browser-option-command

Based on my understanding, It's means we could override the internal pkg name by using this option.

However, based on my experiments:

test('androidDevice.launchBrowser', async function({ androidDevice }) {
  test.slow();
  const context = await androidDevice.launchBrowser({command: 'org.chromium.chrome'});
  const [page] = context.pages();
  await page.goto('data:text/html,<title>Hello world!</title>');
  expect(await page.title()).toBe('Hello world!');
  await context.close();
});

The command config doesn't work. It's not passed to the Android server impl.

In the packages/playwright-core/src/protocol/validator.ts, seems the command option is not a valid parameter for AndroidDeviceLaunchBrowserParams.

Also, I found that in the packages/playwright-core/src/server/dispatchers/androidDispatcher.ts, it's using the params.pkg rather command to get the Android pkg name to run.

Expected behavior

I'm not sure if it's an expected behavior.

Actual behavior

It's always starting the chrome browser.

Additional context

No response

Environment

(Not related)

[Skn0tt]

Looks like a docs issue to me. Let me take a look.