chore(deps, cpp): update ms-vscode.cmake-tools, sonarsource.sonarlint-vscode

[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 sonarsource.sonarlint-vscode from 4.15.0 to 4.16.0

Release notes

• Update Go analyzer 1.18 -> 1.19
• Update PHP analyzer 3.42 -> 3.43 -> 3.44
• Update C# analyzer 10.4 -> 10.5 -> 10.6
• Update CFamily analyzer 6.62 -> 6.63
• Update IaC analyzer 1.41 -> 1.42 -> 1.43
• Update Text analyzer 2.20 -> 2.21
• Update Java analyzer 8.9 -> 8.10
• Update JS/TS/CSS analyzer 10.20 -> 10.21

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

Release notes

1.20

Features:

• Add support for Presets v9, which enables more macro expansion for the include field. #3946
• Add support to configure default folder in workspace setting. #1078
• Add support to configure default folder in workspace setting. #1078 @sanore
• Add support for processing LCOV based coverage info files when tests are
  executed. This adds test execution type, "Run with coverage", on the ctest
  section of the Testing tab.
  #4040
• Add basic CMake language services: quick hover and completions for CMake built-ins. PR #4204
• Add an option to scan kits from a folder. #4191 @std-microblock

Improvements:

• Add ability to pass custom target to "CMake: Build Target" command as argument. #3598 @hippo91
• Fix "Unable to resolve configuration with compilerPath" issue for Swift. #4097
• Ensure that any uses of proc.spawn work, especially for .bat and .cmd files, due to VS Code updating to Node 20. #4037
• Fix "Test output isn't visible when failed" and also mark skipped tests as so. #4116 @redstrate
• Ensure that stopping tests actually forces the tests to stop running. #2095
• Retire the Show Options Moved Notification #4039
• Improve the pinned commands experience by defaulting settings and using VS Code state rather than modifying user settings. #3977
• Skip project building in the CTest test explorer when cmake.buildBeforeRun is set to false. #4241 @Dabsunter
• Improve consistency in key bindings. #4124 @alex20230721

Bug Fixes:

• Fix issue where files don't show up in the outline if any in the group are generated. #4099
• Fix issue where setting test suite delimiter prevent execution of all tests. #4092 @hippo91
• Fix our setting of isUserPreset for presets, only set it to true if it's defined in a user presets file. #4059
• Fix issue where duplicate presets are being listed in dropdown. #4104
• Ensure that we're sanitizing paths for cmake.copyCompileCommands. #3874
• Ensure that tests are updated after a build. #4148
• Fix various GCC compiler errors and GCC linker errors not showing up in Problems View #2864 @0xemgy
• Fix reloading presets when included files are changed or renamed and updated. #3963
• Fix the usage of toolset and archiecture in presets without generator set. #4181
• Fix compilation database path comparison with the cmake.copyCompileCommands that could otherwise overwrite that file. #4207 @k0zmo
• Fix parsing of CMakeUserPresets.json containing configure preset that is referenced in workflow preset. #4202 @nikobockerman
• Fix auto select active project corner case. #4146 Contributed by STMicroelectronics
• Fix issue where starting a CMake Configure with CMake Debugger while there was already a configure process running left a debug session going without a way to stop it. #4230

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

OS/Platform	Previous Size	Current Size	Delta
linux/amd64	482.57M	482.57M	0.00 (+0.00%)
linux/arm64	621.60M	621.60M	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:68a792aad9f59f1eb0608c9ea9549e6b2ea5350a8ee0cf52b9e5cc9bf22329fe

OS/Platform	Previous Size	Current Size	Delta
linux/amd64	695.53M	695.53M	-463.00 (-0.00%)
linux/arm64	677.08M	677.08M	106.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.87s
✅ JSON	npm-package-json-lint	yes		no	0.36s
✅ JSON	prettier	15	1	0	0.35s
✅ JSON	v8r	14		0	8.88s
✅ MARKDOWN	markdownlint	8	0	0	0.84s
✅ MARKDOWN	markdown-table-formatter	8	0	0	0.24s
✅ REPOSITORY	checkov	yes		no	15.0s
✅ REPOSITORY	gitleaks	yes		no	0.89s
✅ REPOSITORY	git_diff	yes		no	0.01s
✅ REPOSITORY	grype	yes		no	9.59s
✅ REPOSITORY	secretlint	yes		no	0.98s
✅ REPOSITORY	syft	yes		no	1.26s
✅ REPOSITORY	trivy	yes		no	5.02s
✅ REPOSITORY	trivy-sbom	yes		no	0.08s
✅ REPOSITORY	trufflehog	yes		no	2.55s
✅ SPELL	lychee	58		0	1.45s
✅ YAML	prettier	22	0	0	0.64s
✅ YAML	v8r	22		0	6.45s
✅ YAML	yamllint	22		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.4.2 (61 linters)
• oxsecurity/megalinter/flavors/dotnetweb@v8.4.2 (70 linters)

[github-actions]

Test Results

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

Results for commit 9287c9c. ± Comparison against base commit fc8fc47.

[github-actions]

Pull Request Report (#727)

Static measures

Description	Value
Number of added lines	2
Number of deleted lines	2
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)	2.5 Days
Time that was spend on the branch before the PR was created	3 Sec
Time that was spend on the branch before the PR was merged	2.5 Days
Time to merge after last review	2.2 Hours

Status check related measures

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