chore(deps, cpp): update github.vscode-pull-request-github, ms-playwright.playwright in devcontainer.json

[philips-software-forest-releaser]

Note

Before merging this PR, please conduct a manual test checking basic functionality of the updated plug-ins. There are limited automated tests for the VS Code Extension updates.

Updates ms-playwright.playwright from 1.1.15 to 1.1.16

Release notes

What's Changed

• Added native support for Plug'n'Play module resolution, including Yarn Berry and PNPM (https://www.github.com/microsoft/playwright-vscode/pull/675)
• Added node_modules/.bin to the webserver PATH environment variable, bringing it in line with npx behavior (https://www.github.com/microsoft/playwright-vscode/pull/671)
• Dropped support for Playwright 1.43 (April 2024) and earlier versions (https://www.github.com/microsoft/playwright-vscode/pull/652)
• Improved configuration file selection and sorting behavior (https://www.github.com/microsoft/playwright-vscode/pull/670, https://www.github.com/microsoft/playwright-vscode/pull/689)
• Polished the user interface with several visual and accessibility improvements (https://www.github.com/microsoft/playwright-vscode/pull/672, https://www.github.com/microsoft/playwright-vscode/pull/657, https://www.github.com/microsoft/playwright-vscode/pull/665, https://www.github.com/microsoft/playwright-vscode/pull/680)
• Fixed various bugs related to debugging, browser lifecycle management, accessibility attributes, and configuration handling (https://www.github.com/microsoft/playwright-vscode/pull/687, https://www.github.com/microsoft/playwright-vscode/pull/685, https://www.github.com/microsoft/playwright-vscode/pull/676, https://www.github.com/microsoft/playwright-vscode/pull/656, https://www.github.com/microsoft/playwright-vscode/pull/644)

Full Changelog: https://www.github.com/microsoft/playwright-vscode/compare/v1.1.15...v1.1.16

Updates github.vscode-pull-request-github from 0.118.2 to 0.120.0

Release notes

0.120.0

Changes

• The #openPullRequest tool recognizes open PR diffs and PR files as being the "open pull request".
• All Copilot PR notifications can be marked as ready using the right-click context menu on the Copilot section header in the Pull Requests view.
• The setting githubIssues.issueAvatarDisplay can be used to control whether the first assignee's avatar or the author's avatar is shown in the Issues view.
• Instead of always running the pull request queries that back the Pull Requests view when refreshing, we now check to see if there are new PRs in the repo before running the queries. This should reduce API usage when there are no new PRs.
• The "Copy link" action is back near the PR title in the pull request description webview.
• You can configure that the default branch is pulled when you're "done" with a PR using "githubPullRequests.postDone": "checkoutDefaultBranchAndPull".

Fixes

• Unable to get list of users to assign them to a pull request. https://www.github.com/microsoft/vscode-pull-request-github/issues/7908
• Error notifications when using GitHub Enterprise Server. https://www.github.com/microsoft/vscode-pull-request-github/issues/7901
• Ignore worktrees that aren't in one of the workspace folders. https://www.github.com/microsoft/vscode-pull-request-github/issues/7896
• Typing "#" and then Enter or Tab opens the GitHub issue queries settings. https://www.github.com/microsoft/vscode-pull-request-github/issues/7838
• Unexpected branch switching when githubIssues.useBranchForIssues = off. https://www.github.com/microsoft/vscode-pull-request-github/issues/7827
• Extension enters rapid refresh loop, causing high API usage and rate limiting. https://www.github.com/microsoft/vscode-pull-request-github/issues/7816
• GitHub PR view highlights all repos with Copilot notification. https://www.github.com/microsoft/vscode-pull-request-github/issues/7852
• Wrong commit is checked out when local branch exists with the same name. https://www.github.com/microsoft/vscode-pull-request-github/issues/7702
• Visual Label not provided for "Title" and "Description" field. https://www.github.com/microsoft/vscode-pull-request-github/issues/7595
• VSCode unresponsive during GitHub Pull Requests PR checkout (large number of files changed). https://www.github.com/microsoft/vscode-pull-request-github/issues/6952
• extension explodes and kicks back out to GITHUB: LOGIN when non github repos are in working directory (specifically codeberg). https://www.github.com/microsoft/vscode-pull-request-github/issues/6945

[github-actions]

Test Results

 5 files  ±0   5 suites  ±0   3m 38s ⏱️ +2s
31 tests ±0  31 ✅ ±0  0 💤 ±0  0 ❌ ±0 
65 runs  ±0  65 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 88bd2fb. ± Comparison against base commit e430762.

♻️ This comment has been updated with latest results.

[github-actions]

✅MegaLinter analysis: Success

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
✅ ACTION	actionlint	20		0	0	0.6s
✅ DOCKERFILE	hadolint	2		0	0	0.77s
✅ GHERKIN	gherkin-lint	6		0	0	2.28s
✅ JSON	npm-package-json-lint	yes		no	no	0.37s
✅ JSON	prettier	15	2	0	0	0.36s
✅ JSON	v8r	15		0	0	16.08s
✅ MARKDOWN	markdownlint	10	0	0	0	0.92s
✅ MARKDOWN	markdown-table-formatter	10	0	0	0	0.2s
✅ REPOSITORY	gitleaks	yes		no	no	0.63s
✅ REPOSITORY	git_diff	yes		no	no	0.01s
✅ REPOSITORY	grype	yes		no	no	27.75s
✅ REPOSITORY	secretlint	yes		no	no	0.98s
✅ REPOSITORY	syft	yes		no	no	1.94s
✅ REPOSITORY	trivy	yes		no	no	6.89s
✅ REPOSITORY	trivy-sbom	yes		no	no	0.24s
✅ REPOSITORY	trufflehog	yes		no	no	3.76s
✅ SPELL	lychee	70		0	0	10.95s
✅ YAML	prettier	26	0	0	0	0.79s
✅ YAML	v8r	26		0	0	6.77s
✅ YAML	yamllint	26		0	0	0.74s

See detailed reports in MegaLinter artifacts

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

• Documentation: Custom Flavors
• Command: npx [email protected] --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,DOCKERFILE_HADOLINT,GHERKIN_GHERKIN_LINT,JSON_V8R,JSON_PRETTIER,JSON_NPM_PACKAGE_JSON_LINT,MARKDOWN_MARKDOWNLINT,MARKDOWN_MARKDOWN_TABLE_FORMATTER,REPOSITORY_GIT_DIFF,REPOSITORY_GITLEAKS,REPOSITORY_GRYPE,REPOSITORY_SECRETLINT,REPOSITORY_SYFT,REPOSITORY_TRIVY,REPOSITORY_TRIVY_SBOM,REPOSITORY_TRUFFLEHOG,SPELL_LYCHEE,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R

[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]

📦 Container Size Analysis

Note

Comparing ghcr.io/philips-software/amp-devcontainer-rust:edge ➔ ghcr.io/philips-software/amp-devcontainer-rust:pr-970

📈 Size Comparison Table

OS/Platform	Previous	Current	Change	Trend
linux/amd64	539.33 MB	539.33 MB	277 B (0%)	🔽
linux/arm64	498.75 MB	495.81 MB	2.94 MB (-0.59%)	🔽

[github-actions]

📦 Container Size Analysis

Note

Comparing ghcr.io/philips-software/amp-devcontainer-cpp:edge ➔ ghcr.io/philips-software/amp-devcontainer-cpp:pr-970

📈 Size Comparison Table

OS/Platform	Previous	Current	Change	Trend
linux/amd64	693.5 MB	693.5 MB	585 B (0%)	🔽
linux/arm64	676.55 MB	676.55 MB	+169 B (+0%)	🔼

[github-actions]

Pull Request Report (#970)

Static measures

Description	Value
Number of added lines	2
Number of deleted lines	2
Number of changed files	1
Number of commits	2
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	5

Time related measures

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

Status check related measures

Description	Value
Total runtime for last status check run (Workflow for PR)	39.4 Min
Total time spend in last status check run on PR	12.2 Min

[github-actions]

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