Update playwright monorepo to v1.48.2

[matticbot]

This started as an automated Renovate PR (my first one!), but it seems there are various issues. In particular, there were timeouts on various E2E tests, and Storybook tests failed due to locale bugs (despite running fine locally).

As such, I've set it to match Calypso for now (1.48.2), as they also reported issues: Automattic/wp-calypso#97275

---

This PR contains the following updates:

Package	Type	Update	Change
@playwright/test (source)	devDependencies	minor	1.45.1 -> 1.48.2
playwright (source)	devDependencies	minor	1.45.1 -> 1.48.2
playwright-core (source)	devDependencies	patch	1.49.0 -> 1.49.1

---

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WordPress.com Simple site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin, and enable the renovate/playwright-monorepo branch.

  • For jetpack-mu-wpcom changes, also add define( 'JETPACK_MU_WPCOM_LOAD_VIA_BETA_PLUGIN', true ); to your wp-config.php file.

• To test on Simple, run the following command on your sandbox:

  bin/jetpack-downloader test jetpack renovate/playwright-monorepo
  

  bin/jetpack-downloader test jetpack-mu-wpcom-plugin renovate/playwright-monorepo
  

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[matticbot]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[anomiex]

Looks like a reasonable upgrade. I wonder what's broken with 1.49 though.

[tbradsha]

I wonder what's broken with 1.49 though.

The two issues I observed:

• Invalid locale passed to Intl.NumberFormatter (likely this, which in turn may be a Chromium bug: [Bug]: Chromium returns "en-US@posix" for navigator.language microsoft/playwright#34046)
• Timeouts (may be coincidental)