test(deps): bump the npm group with 2 updates

[dependabot]

Bumps the npm group with 2 updates: @playwright/test and @types/node.

Updates @playwright/test from 1.48.2 to 1.49.0

Release notes

Sourced from @​playwright/test's releases.

v1.49.0

Aria snapshots

New assertion expect(locator).toMatchAriaSnapshot() verifies page structure by comparing to an expected accessibility tree, represented as YAML.

await page.goto('https://playwright.dev');
await expect(page.locator('body')).toMatchAriaSnapshot(`
  - banner:
    - heading /Playwright enables reliable/ [level=1]
    - link "Get started"
    - link "Star microsoft/playwright on GitHub"
  - main:
    - img "Browsers (Chromium, Firefox, WebKit)"
    - heading "Any browser • Any platform • One API"
`);

You can generate this assertion with Test Generator and update the expected snapshot with --update-snapshots command line flag.

Learn more in the aria snapshots guide.

Test runner

• New option testConfig.tsconfig allows to specify a single tsconfig to be used for all tests.
• New method test.fail.only() to focus on a failing test.
• Options testConfig.globalSetup and testConfig.globalTeardown now support multiple setups/teardowns.
• New value 'on-first-failure' for testOptions.screenshot.
• Added "previous" and "next" buttons to the HTML report to quickly switch between test cases.
• New properties testInfoError.cause and testError.cause mirroring Error.cause.

Breaking: channels chrome, msedge and similar switch to new headless

This change affects you if you're using one of the following channels in your playwright.config.ts:

• chrome, chrome-dev, chrome-beta, or chrome-canary
• msedge, msedge-dev, msedge-beta, or msedge-canary

What do I need to do?

After updating to Playwright v1.49, run your test suite. If it still passes, you're good to go. If not, you will probably need to update your snapshots, and adapt some of your test code around PDF viewers and extensions. See [issue #33566](microsoft/playwright#33566) for more details.

Other breaking changes

• There will be no more updates for WebKit on Ubuntu 20.04 and Debian 11. We recommend updating your OS to a later version.
• Package @playwright/experimental-ct-vue2 will no longer be updated.
• Package @playwright/experimental-ct-solid will no longer be updated.

Try new Chromium headless

You can opt into the new headless mode by using 'chromium' channel. As official Chrome documentation puts it:

New Headless on the other hand is the real Chrome browser, and is thus more authentic, reliable, and offers more features. This makes it more suitable for high-accuracy end-to-end web app testing or browser extension testing.

... (truncated)

Commits

• a70a96a chore: mark v1.49.0 (#33649)
• 53f51a8 cherry-pick(#33638): chore: clear highlight when performing action
• 2a00ca8 cherry-pick(#33635): chore: add cm placeholder text
• 0e64340 cherry-pick(#33632): chore: highlight edited locator while recording
• cb0f456 cherry-pick(#33629): fix(rebase): do not apply multiple rebaselines to the sa...
• 698823a cherry-pick(#33627): fix(codegen): document.documentElement is null on early ...
• c0fa804 cherry-pick(#33619): fix(aria): normalize whitespace in toMatchAccessible{Nam...
• 7a32228 cherry-pick(#33614): docs: add ariaSnapshot.timeout for language ports (#33615)
• 0e31ace cherry-pick(#33575): fix(canvas snapshots): position mismatch in headless mode
• b2a39ff cherry-pick(#33604): docs: update docs about headless shell
• Additional commits viewable in compare view

Updates @types/node from 22.9.0 to 22.9.3

Commits

• See full diff 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Compressed layer size comparison

Comparing ghcr.io/philips-software/amp-devcontainer-rust:latest to ghcr.io/philips-software/amp-devcontainer-rust@sha256:60b2e1a9964845339c6d48e0d362befe5027fe08df95eaa559432b09602d65c8

OS/Platform	Previous Size	Current Size	Delta
linux/amd64	459.82M	458.77M	-1.05M (-0.23%)
linux/arm64	599.31M	598.30M	-1.02M (-0.17%)

[github-actions]

Compressed layer size comparison

Comparing ghcr.io/philips-software/amp-devcontainer-cpp:latest to ghcr.io/philips-software/amp-devcontainer-cpp@sha256:e0cccda20007239b015ccb0529368785e12e29d77df232c3ab4be828c4978410

OS/Platform	Previous Size	Current Size	Delta
linux/amd64	650.48M	650.10M	-389.02K (-0.06%)
linux/arm64	643.16M	642.84M	-330.90K (-0.05%)

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	16		0	0.09s
✅ DOCKERFILE	hadolint	2		0	0.59s
✅ GHERKIN	gherkin-lint	2		0	0.74s
✅ JSON	npm-package-json-lint	yes		no	0.32s
✅ JSON	prettier	15	1	0	0.4s
✅ JSON	v8r	14		0	14.75s
✅ MARKDOWN	markdownlint	8	0	0	0.68s
✅ MARKDOWN	markdown-table-formatter	8	0	0	0.26s
✅ REPOSITORY	checkov	yes		no	16.44s
✅ REPOSITORY	gitleaks	yes		no	0.24s
✅ REPOSITORY	git_diff	yes		no	0.01s
✅ REPOSITORY	grype	yes		no	9.35s
✅ REPOSITORY	secretlint	yes		no	0.98s
✅ REPOSITORY	syft	yes		no	1.33s
✅ REPOSITORY	trivy	yes		no	9.99s
✅ REPOSITORY	trivy-sbom	yes		no	0.08s
✅ REPOSITORY	trufflehog	yes		no	3.1s
✅ SPELL	lychee	57		0	1.88s
✅ YAML	prettier	21	0	0	0.81s
✅ YAML	v8r	21		0	12.36s
✅ YAML	yamllint	21		0	0.55s

See detailed report in MegaLinter reports

You could have the same capabilities but better runtime performances if you use a MegaLinter flavor:

• oxsecurity/megalinter/flavors/[email protected] (62 linters)
• oxsecurity/megalinter/flavors/[email protected] (71 linters)

MegaLinter is graciously provided by

[github-actions]

Test Results

 2 files  ±0   2 suites  ±0   1m 24s ⏱️ +3s
29 tests ±0  29 ✅ ±0  0 💤 ±0  0 ❌ ±0 
31 runs  ±0  31 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 70c7505. ± Comparison against base commit 991644c.

[github-actions]

Pull Request Report (#649)

Static measures

Description	Value
Number of added lines	18
Number of deleted lines	18
Number of changed files	2
Number of commits	1
Number of reviews	1
Number of comments (w/o review comments)	5
Number of reviews that contains a comment to resolve	0
Number of reviews that requested a change from the author	0
Number of reviews that approved the Pull Request	1
Get the total number of participants of a Pull Request	4

Time related measures

Description	Value
PR lead time (from creation to close of PR)	1.2 Hours
Time that was spend on the branch before the PR was created	1 Sec
Time that was spend on the branch before the PR was merged	1.2 Hours
Time to merge after last review	1 Hours

Status check related measures

Description	Value
Total runtime for last status check run (Workflow for PR)	18.4 Min
Total time spend in last status check run on PR	1.1 Hours

[github-actions]

🎉 Hooray! The changes in this pull request went live with the release of v5.5.1 🎉