Add support for custom Chrome args in launchBrowser

[konard]

Feature Request

Summary

Add support for custom Chrome arguments (like --no-sandbox, --disable-setuid-sandbox) in the launchBrowser function for headless server environments.

Problem

Currently, launchBrowser uses a fixed set of CHROME_ARGS from constants.js:

export const CHROME_ARGS = [
  '--disable-session-crashed-bubble',
  '--hide-crash-restore-bubble',
  '--disable-infobars',
  '--no-first-run',
  '--no-default-browser-check',
  '--disable-crash-restore',
];

However, when running in headless server environments (Docker containers, CI/CD, etc.), additional arguments are often required:

• --no-sandbox
• --disable-setuid-sandbox
• --disable-dev-shm-usage

Without these args, the browser fails to launch with errors like:

No usable sandbox! If you are running on Ubuntu 23.10+ or another Linux distro that has disabled unprivileged user namespaces with AppArmor...

Proposed Solution

Allow passing custom args in the options parameter of launchBrowser:

const { browser, page } = await launchBrowser({
  engine: 'puppeteer',
  headless: true,
  args: ['--no-sandbox', '--disable-setuid-sandbox'], // Custom args to append
});

Use Case

This feature is needed for web-capture integration, which runs in Docker containers and needs sandbox-disabled Chrome for headless rendering.

Current Workaround

Currently, consumers must maintain their own browser launch code that duplicates browser-commander's logic while adding the necessary server-side args.

Alternatives Considered

1. Adding server-side args to the default CHROME_ARGS - but this might not be desired for all use cases
2. Providing a separate CHROME_SERVER_ARGS export - less flexible than option 1

---

Related PR: link-assistant/web-capture#25

[konard]

Ok, we can keep current settings by default and for backward compatibility, as they produce nice screenshots of the browsers, but for headless and other use cases we sure need add configuration.