chore(deps, cpp): update ms-vscode.cpptools

[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-vscode.cpptools from 1.23.5 to 1.23.6

Release notes

Instructions

The extension can be obtained by one of the methods below:

• Install the "C/C++" or "C/C++ Extension Pack" extension published by Microsoft from the Extensions view in VS Code.
• Download a vsix that matches your OS from the Assets section below (and install it via the method mentioned above). The previous download methods have the vsix signatures verified by the Marketplace, but for this method, you can do the verification by downloading the matching manifest and signature.p7s file and running npx [at]vscode/vsce@latest verify-signature -i <.vsix> -m <.signature.manifest> -s <.signature.p7s> vscode-vsce#1044.

Requirements

• VS Code 1.67.0 or later (April 2022).
• Windows 7+ (x64, arm64), macOS 10.12+, Linux (Ubuntu 16+, etc.).
  • Debugging is not supported on CentOS 7 or RHEL 7. The last supported version was 1.22.11: #13219.

Changes

Bug Fixes

• Fix a bug with remote attach debugging. #13137
• Fix symlink-related regression bugs. #13214, #13228
• Fix a regression bug when using 'Select IntelliSense Configuration'. #13220
• Fix a regression bug with files.associations handling. #13223

[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:c48067b4766a61310b1b5ca5fcf61569bd59dd0227d39e13bb7c679a8906c154

OS/Platform	Previous Size	Current Size	Delta
linux/amd64	475.28M	475.28M	0.00 (+0.00%)
linux/arm64	614.64M	614.64M	0.00 (+0.00%)

[github-actions]

Compressed layer size comparison

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

OS/Platform	Previous Size	Current Size	Delta
linux/amd64	686.88M	686.88M	0.00 (+0.00%)
linux/arm64	668.62M	668.62M	0.00 (+0.00%)

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	17		0	0.07s
✅ DOCKERFILE	hadolint	2		0	0.49s
✅ GHERKIN	gherkin-lint	2		0	0.88s
✅ JSON	npm-package-json-lint	yes		no	0.34s
✅ JSON	prettier	15	1	0	0.34s
✅ JSON	v8r	14		0	8.48s
✅ MARKDOWN	markdownlint	8	0	0	0.86s
✅ MARKDOWN	markdown-table-formatter	8	0	0	0.22s
✅ REPOSITORY	checkov	yes		no	13.97s
✅ REPOSITORY	gitleaks	yes		no	0.88s
✅ REPOSITORY	git_diff	yes		no	0.01s
✅ REPOSITORY	grype	yes		no	9.43s
✅ REPOSITORY	secretlint	yes		no	1.0s
✅ REPOSITORY	syft	yes		no	1.19s
✅ REPOSITORY	trivy	yes		no	5.06s
✅ REPOSITORY	trivy-sbom	yes		no	0.08s
✅ REPOSITORY	trufflehog	yes		no	2.66s
✅ SPELL	lychee	58		0	6.44s
✅ YAML	prettier	22	0	0	0.61s
✅ YAML	v8r	22		0	5.98s
✅ YAML	yamllint	22		0	0.4s

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/dotnet@v8.4.2 (61 linters)
• oxsecurity/megalinter/flavors/dotnetweb@v8.4.2 (70 linters)

[github-actions]

Test Results

 2 files  ±0   2 suites  ±0   1m 18s ⏱️ -1s
29 tests ±0  29 ✅ ±0  0 💤 ±0  0 ❌ ±0 
31 runs  ±0  31 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 7ea836b. ± Comparison against base commit 178ee21.

[github-actions]

Pull Request Report (#713)

Static measures

Description	Value
Number of added lines	1
Number of deleted lines	1
Number of changed files	1
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)	12.7 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	12.7 Hours
Time to merge after last review	1.8 Hours

Status check related measures

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

[github-actions]

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