Feature: 📱Mobile Emulation

[tkadlec]

We definitely need to get some mobile emulation in place. Playwright has a long list of device descriptors (https://github.com/microsoft/playwright/blob/main/packages/playwright-core/src/server/deviceDescriptorsSource.json) which we could expose, or we could go with our own subset.

Either way, will want to make sure there's a good default cpuThrottle level applied for each as well.

[mjkozicki]

For the mobile emulation, let's expand to all device profiles offered OOB from Playwright.
Command line addition of -d, --device or --deviceType or deviceEmulation - I am open to other options on this as well. I prefer the shorter --device but if there are possible future conflicts, let's try to think of them now.

The structure of the Playwright device profile is

{
  "<device_profilename>": {
    "userAgent": "<user_agent>:string",
    "viewport": {
      "width": <int>,
      "height": <int>
    },
    "deviceScaleFactor": <int>,
    "isMobile": <boolean>,
    "hasTouch": <boolean>,
    "defaultBrowserType": "<browser>:string"
  },
...
}

Any specifically set values in the CLI should override the provided profile (if possible).

[sergeychernyshev]

-d and —device is a good option.

Who knows, maybe we’ll have a way to drive real devices later.

I imagine when we do add real devices, it’ll have to come with some external configuration file so we’ll add that as a backward compatible variation.

[sergeychernyshev]

Almost there, just need to set defaultBrowserType now (see separate #246 ticket).

[sergeychernyshev]

@tkadlec we are not doing CPU throttle as part of these right now - do you want to write up a separate ticket for it with some guidance on what to use for each?