Command launch-browser-server do not start in headed mode

Nobody has claimed this yet.

**Describe the bug**
A clear and concise description of what the bug is.

**To Reproduce**
Steps to reproduce the behavior:
1. Create a new project
```powershell
uv init
```
2. Install dependencies
```powershell
uv add robotframework-browser[bb]
uv run rfbrowser install chromium
```
4. Run
```powershell
uv run rfbrowser launch-browser-server chromium headless=False port=9222 wsPath=chromium/1`
```
7. No error process start but not in headed mode**Expected behavior**See the chrome debug window

**Desktop (please complete the following information):**
- OS: win11
- Browser [e.g. chrome, safari]
- Version `uv run rfbowser --version`
```powershell
======================================================================
Installed Browser library version is: "19.12.3"
Installed Robot Framework version: "7.4.1"
Required Playwright is: "1.57.0"
======================================================================
```

**Workaround**
Start chrome debug using the following powershell command.
```powershell
Start-Process chrome.exe -ArgumentList "--remote-debugging-port=9222", "--user-data-dir=$env:TEMP\chrome-robot-debug", "--no-first-run", "--no-default-browser-check", "--start-maximized", "--ignore-https-error"
```

Start by reproducing the Windows command `uv run rfbrowser launch-browser-server chromium headless=False port=9222 wsPath=chromium/1` and trace the `launch-browser-server` entry point's handling of `headless=False`. Compare the behavior with the documented workaround; done means the command opens a visible Chromium debug window on port 9222.

Written by the indexing model from the issue text.