Provides device emulation via --deviceName flag using playwright

[MildMax]

• Provides new flag --device to allow device emulation
• Users are allowed to provide custom viewports that override device defaults via --width and --height CLI args
• Updates playwright to 1.58.2 as part of bug fix for isMobile spawning multiple ffmpeg processes on chromium browsers in 1.57.0
• Omits chrome-canary and chrome-beta from device emulation unit tests, adds note to README indicating telescope does not support device emulation for the chrome beta and chrome canary browsers
• Sets node version 24 to help with mobile emulation in chrome browsers

Closes #4

[sergeychernyshev]

Hey @MildMax, can you update the PR description with what else you did in this PR (I see that you upgraded playwright - was it needed for something specific?).

Also, can you link the issue in this PR as well?

[sergeychernyshev]

I also see extra space, please run the npm run format on it.

[sergeychernyshev]

All looks great and straightforward with just a couple comments.

Still getting

Jest did not exit one second after the test run has completed.

'This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue.

[sergeychernyshev]

My TypeScript complains that SuccessfulTestResult is only used for types and should be imported separately as such.

[Judyzc]

All looks great and straightforward with just a couple comments.

Still getting

Jest did not exit one second after the test run has completed.

'This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue.

I got the same thing with jest and that's about it

[Judyzc]

All looks great and straightforward with just a couple comments.
Still getting

Jest did not exit one second after the test run has completed.

'This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue.

I got the same thing with jest and that's about it

I'm no longer getting this timeout warning

[MildMax]

moved to draft and paused due to issues with hanging processes when emulating devices on chromium based browsers