build(deps-dev): bump @playwright/test from 1.31.0 to 1.33.0

[dependabot]

Bumps @playwright/test from 1.31.0 to 1.33.0.

Release notes

Sourced from @​playwright/test's releases.

v1.33.0

Locators Update

• Use [locator.or()] to create a locator that matches either of the two locators. Consider a scenario where you'd like to click on a "New email" button, but sometimes a security settings dialog shows up instead. In this case, you can wait for either a "New email" button, or a dialog and act accordingly:

  const newEmail = page.getByRole('button', { name: 'New' });
  const dialog = page.getByText('Confirm security settings');
  await expect(newEmail.or(dialog)).toBeVisible();
  if (await dialog.isVisible())
    await page.getByRole('button', { name: 'Dismiss' }).click();
  await newEmail.click();

• Use new options hasNot and hasNotText in [locator.filter()] to find elements that do not match certain conditions.

  const rowLocator = page.locator('tr');
  await rowLocator
      .filter({ hasNotText: 'text in column 1' })
      .filter({ hasNot: page.getByRole('button', { name: 'column 2 button' }) })
      .screenshot();

• Use new web-first assertion [locatorAssertions.toBeAttached()] to ensure that the element is present in the page's DOM. Do not confuse with the [locatorAssertions.toBeVisible()] that ensures that element is both attached & visible.

New APIs

• [locator.or()]
• New option hasNot in [locator.filter()]
• New option hasNotText in [locator.filter()]
• [locatorAssertions.toBeAttached()]
• New option timeout in [route.fetch()]
• [reporter.onExit()]

⚠️ Breaking change

• The mcr.microsoft.com/playwright:v1.33.0 now serves a Playwright image based on Ubuntu Jammy. To use the focal-based image, please use mcr.microsoft.com/playwright:v1.33.0-focal instead.

Browser Versions

• Chromium 113.0.5672.53
• Mozilla Firefox 112.0
• WebKit 16.4

This version was also tested against the following stable channels:

... (truncated)

Commits

• b64516e cherry-pick(#22673): devops: fix workflow publishing
• 2ca4cd0 cherry-pick(#22667): chore(chromium): remove --disable-sync CLI switch
• 0d61e31 chore: mark 1.33.0 (#22602)
• 64bca22 cherry-pick(#22615): docs: release notes 1.33
• 9a3c4e4 cherry-pick(#22628): docs: add UI mode doc (#22632)
• adef765 cherry-pick(#22609): chore: fix list-files
• eed6c33 feat(webkit): roll to r1837 (#22566)
• 05b113f docs: add warning to locator.all (#22537)
• 62bd419 chore: cleanup bandaid firefox pref (#22570)
• 99d4887 feat(firefox): roll to r1403 (#22540)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #616.