feat(api): add launchOptions support to ConnectOptions

[RaHehl]

Add ability to pass LaunchOptions directly via ConnectOptions instead of manually constructing JSON headers.

The implementation automatically serializes launchOptions to the x-playwright-launch-options header when provided.

Motivation / Use case

When running the browser inside a container and connecting remotely (see Playwright docs: Remote connection with Docker), it’s currently cumbersome to specify the browser channel.

current:
connectOptions.headers.put("x-playwright-launch-options", "{\"channel\":\"msedge\"}");
which you have to discover first

Proposed API (Java)

browserType.connect("ws://localhost:3000/ws",
          new BrowserType.ConnectOptions().setLaunchOptions(
            new BrowserType.LaunchOptions().setChannel("msedge")));

[RaHehl]

@microsoft-github-policy-service agree

[yury-s]

This file is generated from https://github.com/microsoft/playwright/blob/main/docs/src/api/class-browsertype.md, please don't edit it manually. I also suggest you start with filing a new issue in https://github.com/microsoft/playwright with a description of the problem.

x-playwright-launch-options is currently a private property. If we want to expose it in the API it should be available in other ports too, in Node.js in the first place. Let's assess the use case first.