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

[embedded-releaser-app]

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

0 files   -  4  0 suites   - 4   0s ⏱️ - 2m 22s
0 tests  - 30  0 ✅  - 30  0 💤 ±0  0 ❌ ±0 
0 runs   - 64  0 ✅  - 64  0 💤 ±0  0 ❌ ±0 

Results for commit 3c976c6. ± Comparison against base commit 8aff842.

[github-actions]

✅⚠️MegaLinter analysis: Success with warnings

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
✅ ACTION	actionlint	19		0	0	0.6s
✅ DOCKERFILE	hadolint	2		0	0	0.85s
✅ GHERKIN	gherkin-lint	6		0	0	2.21s
✅ JSON	npm-package-json-lint	yes		no	no	0.48s
✅ JSON	prettier	16	2	0	0	0.56s
✅ JSON	v8r	16		0	0	7.3s
⚠️ MARKDOWN	markdownlint	9	0	1	0	0.8s
✅ MARKDOWN	markdown-table-formatter	9	1	0	0	0.22s
✅ REPOSITORY	gitleaks	yes		no	no	1.31s
✅ REPOSITORY	git_diff	yes		no	no	0.01s
✅ REPOSITORY	grype	yes		no	no	27.87s
✅ REPOSITORY	secretlint	yes		no	no	0.98s
✅ REPOSITORY	syft	yes		no	no	2.0s
✅ REPOSITORY	trivy	yes		no	no	4.64s
✅ REPOSITORY	trivy-sbom	yes		no	no	0.24s
✅ REPOSITORY	trufflehog	yes		no	no	2.93s
✅ SPELL	lychee	70		0	0	11.53s
✅ YAML	prettier	25	0	0	0	1.14s
✅ YAML	v8r	25		0	0	7.74s
✅ YAML	yamllint	25		0	0	0.7s

Detailed Issues

⚠️ MARKDOWN / markdownlint - 1 error

.github/CONTRIBUTING.md:18:7 MD051/link-fragments Link fragments should be valid [Context: "[Found a security vulnerability?](#found-a-security-vulnerability)"]

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 mega-linter-runner@9.0.1 --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