Refactor parseBrowserContextOptions to Sobek

[inancgumus]

What?

Refactor parseBrowserContextOptions to use direct Sobek transformation.

Why?

After the refactorings we made in #1270, it's now possible to let Sobek perform this transformation alone.

Checklist

• I have performed a self-review of my code
• I have added tests for my changes (locally tested it—see the script)
• I have commented on my code, particularly in hard-to-understand areas

Script

I also used the script to test it using my old friend Printf in Browser.NewContext etc..

export default async function() {
  const context = await browser.newContext({
    acceptDownloads: true,
    downloadsPath: "/tmp",
    bypassCSP: true,
    colorScheme: "dark",
    deviceScaleFactor: 1,
    extraHTTPHeaders: {
        "X-Header": "value",
    },
    geolocation: { latitude: 51.509865, longitude: -0.118092 },
    hasTouch: true,
    httpCredentials: { username: "admin", password: "password" },
    ignoreHTTPSErrors: true,
    isMobile: true,
    javaScriptEnabled: true,
    locale: "fr-FR",
    offline: true,
    permissions: ["camera", "microphone"],
    reducedMotion: true,
    screen: { width: 800, height: 600 },
    timezoneID: "Europe/Paris",
    userAgent: "my agent",
    viewport: { width: 800, height: 600 },
  });
}

Related PR(s)/Issue(s)

• De-sobekify BrowserContext methods #1270

[ankur22]

It seems like a good idea, but I think we should add another test to ensure that all the fields are parsed/exported/merged as we expect.

The base branch was changed.