chore(deps, cpp): update ms-vscode.cmake-tools, 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.6 to 1.24.5

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

New Feature

• Add support for Copilot descriptions in hover tooltips, controlled by the C_Cpp.copilotHover setting. PR #13385

Enhancements

• Improve/fix the switch header/source feature. #2635
• Add detected test frameworks to the Copilot context when #cpp is used. PR #13285
• Update clang-tidy and clang-format from 19.1.7 to 20.1.2. PR #13348
• Remove some unnecessary files from the vsix. PR #13368
• Improve the logging when a non-existent path is used for indexing. PR #13372
• Add a new recursiveIncludes property to c_cpp_properties.json. PR #13374
• Remove the C_Cpp.updateChannel setting. PR #13376
• Add handling of -cxx-isystem, -stblib++-isystem, -isystem-after, and --include-barrier Clang compiler arguments when composing the order of include paths used by IntelliSense.
• Defer the building of the include completion cache to another thread to improve performance when a file is opened.
• On shutdown, immediately terminate the IntelliSense process instead of waiting 2 seconds.

Bug Fixes

• Fix an IntelliSense crash in build_sections. #12666, #12956
• Fix random IntelliSense process crashes on Linux/macOS when C_Cpp.intelliSenseCacheSize is > 0. #12668
• Fix a bug in which hundreds of custom configuration requests could be sent on startup before the configuration provider has registered. #13166
• Fix handling of the -framework compiler argument. #13204
• Fix a potential race between didChange and didOpen. PR #13209
• Fix an issue with the .editorconfig tab_size. PR #13216
• Fix a potential deadlock on shutdown if configuration providers are used. #13218
• Fix the code analysis mode in the Language Status bar not updating after the setting changes. #13240
• Fix system include/framework paths being used as a fallback for user include/framework paths in the base configuration. PR #13247
• Fix the svdPath description being missing for launch.json. #13287
• Update the Windows SDK packages referenced in the walkthrough. #13290
• Fix an issue with C: being treated as a relative path. PR #13297
• Fix an unnecessary TU reset when a change is detected in a compile_commands.json file that is not used by the active configuration. #13317
• Fix handling of URIs in web environments. #13327
• Fix a potential deadlock after using 'Reset IntelliSense Database'. #13337
• Fix some localization bugs. PR #13373
• Fix IntelliSense showing the wrong size of objects. #13375
• Fix the get_mangled_function_name IntelliSense process crash. #13358
• Fix an issue with duplicate forced includes being removed. Multiple forced includes of the same file should now properly be included multiple times.
• Fix an issue in which the base configuration browse paths may not get populated when using a custom configuration provider.
• Fix an issue with forced includes not being resolved against the same include path search order as a compiler would.
• Fix a ${workspaceFolder}/* include path not being used as a non-recursive browse path.
• Fix an issue with include path ordering of paths specified with the -imsvc argument.
• Fix a race condition that could result in incorrect include completion results.
• Avoid reporting an error due to multiple didOpen requests after a crash.
• Fix an inaccurate cursor position for IntelliSense update.
• Fix an IntelliSense crash if a "bad seq number" occurs.
• Fix processes potentially getting stuck on shutdown.
• Fix a potential crash when saving a file.
• Fix a random crash during code analysis.

Updates ms-vscode.cmake-tools from 1.20.52 to 1.20.53

Release notes

1.20.53

Improvements:

• Add notification suggesting users to uninstall twxs.cmake now that we have built-in Language Services. #4288

Bug Fixes:

• Fix regression where we weren't properly expanding copyCompileCommands path. #4294

[github-actions]

Compressed layer size comparison

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

OS/Platform	Previous Size	Current Size	Delta
linux/amd64	482.86M	482.86M	0.00 (+0.00%)
linux/arm64	434.30M	434.30M	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:75f797e5cba1a03788244f2ef80d50ca49b4ec76f3944404858e0f32b43307c0

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

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
✅ ACTION	actionlint	17		0	0	0.07s
✅ DOCKERFILE	hadolint	2		0	0	0.52s
✅ GHERKIN	gherkin-lint	2		0	0	0.8s
✅ JSON	npm-package-json-lint	yes		no	no	0.33s
✅ JSON	prettier	15	1	0	0	0.35s
✅ JSON	v8r	15		0	0	10.54s
✅ MARKDOWN	markdownlint	8	0	0	0	0.83s
✅ MARKDOWN	markdown-table-formatter	8	0	0	0	0.24s
✅ REPOSITORY	checkov	yes		no	no	14.67s
✅ REPOSITORY	gitleaks	yes		no	no	0.27s
✅ REPOSITORY	git_diff	yes		no	no	0.01s
✅ REPOSITORY	grype	yes		no	no	21.62s
✅ REPOSITORY	secretlint	yes		no	no	0.97s
✅ REPOSITORY	syft	yes		no	no	1.25s
✅ REPOSITORY	trivy	yes		no	no	4.8s
✅ REPOSITORY	trivy-sbom	yes		no	no	0.09s
✅ REPOSITORY	trufflehog	yes		no	no	11.4s
✅ SPELL	lychee	59		0	0	1.39s
✅ YAML	prettier	22	0	0	0	0.69s
✅ YAML	v8r	22		0	0	5.96s
✅ YAML	yamllint	22		0	0	0.42s

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.5.0 (62 linters)
• oxsecurity/megalinter/flavors/dotnetweb@v8.5.0 (71 linters)

[github-actions]

Test Results

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

Results for commit 6d3be0f. ± Comparison against base commit 488fc6d.

♻️ This comment has been updated with latest results.

[Ron (rjaegers)]

Converted to draft as there seem to be issues with the changes in SonarQube for IDE

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

Pull Request Report (#739)

Static measures

Description	Value
Number of added lines	2
Number of deleted lines	2
Number of changed files	1
Number of commits	4
Number of reviews	1
Number of comments (w/o review comments)	6
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	6

Time related measures

Description	Value
PR lead time (from creation to close of PR)	39.2 Days
Time that was spend on the branch before the PR was created	0 Sec
Time that was spend on the branch before the PR was merged	4.2 Days
Time to merge after last review	36.8 Days

Status check related measures

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

[github-actions]

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