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

[philips-software-forest-releaser[bot]]

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

Updates ms-vscode.cpptools from 1.20.5 to 1.21.2

Release notes

## Instructions Install it via using the Extensions view in VS Code or download a vsix that matches your OS from Assets section below (or the "Download" dropdown in the "Version History" tab section on the [Marketplace](https://marketplace.visualstudio.com/items?itemName=ms-vscode.cpptools) website) and then use the `Extensions: Install from VSIX...` command in VS Code (don't double-click the vsix or another app like VS might try to open it incorrectly). ## Requirements * VS Code 1.67.0 or later (April, 2022). * Windows 7+, macOS 10.12+, Linux (Ubuntu 16+, etc.). ## Changes ### Enhancements * Add `see` and `sa` to the `C_Cpp.doxygen.sectionTags` setting. [#12384](https://www.github.com/microsoft/vscode-cpptools/issues/12384) * Update the vcpkg header database. [PR #12430](https://www.github.com/microsoft/vscode-cpptools/pull/12430) * Disable the pre-release prompt if the `extensions.ignoreRecommendations` setting is `true`. [#12438](https://www.github.com/microsoft/vscode-cpptools/issues/12438) * Switch to an alternative workspace symbol search implementation (performance and results will be slightly different from previous versions). * Various IntelliSense engine updates/fixes. ### Bug Fixes * Stop logging file watch events for excluded files. [#11455](https://www.github.com/microsoft/vscode-cpptools/issues/11455) * Fix a crash if the Ryzen 3000 doesn't have updated drivers. [#12201](https://www.github.com/microsoft/vscode-cpptools/issues/12201) * Fix handling of `-isystem` and `-iquote` for IntelliSense configuration. [#12207](https://www.github.com/microsoft/vscode-cpptools/issues/12207) * Fix doxygen comment generation when `/**` comments are used. [#12249](https://www.github.com/microsoft/vscode-cpptools/issues/12249) * Fix a code analysis crash on Linux if the message is too long. [#12285](https://www.github.com/microsoft/vscode-cpptools/issues/12285) * Fix relative paths in `compile_commands.json` to be relative to the `compile_commands.json`'s directory. [#12290](https://www.github.com/microsoft/vscode-cpptools/issues/12290) * Fix a tag parser performance regression. [#12292](https://www.github.com/microsoft/vscode-cpptools/issues/12292) * Fix a regression with cl.exe system include path detection. [#12293](https://www.github.com/microsoft/vscode-cpptools/issues/12293) * Fix code analysis, find all references, and rename from getting the wrong configuration for non-open files on the first run when using a configuration provider. [#12313](https://www.github.com/microsoft/vscode-cpptools/issues/12313) * Fix handling of doxygen comment blocks with `*//*` in them. [#12316](https://www.github.com/microsoft/vscode-cpptools/issues/12316) * Fix potential crashes during IntelliSense process shutdown. [#12354](https://www.github.com/microsoft/vscode-cpptools/issues/12354) * Fix the language status not showing it's busy while the tag parser is initializing. [#12403](https://www.github.com/microsoft/vscode-cpptools/issues/12403) * Fix the vcpkg code action not appearing for missing headers available via vcpkg. [#12413](https://www.github.com/microsoft/vscode-cpptools/issues/12413) * Fix custom configurations sometimes not getting used. [PR #12427](https://www.github.com/microsoft/vscode-cpptools/pull/12427) * Fix a code analysis error when using gcc 14. [#12428](https://www.github.com/microsoft/vscode-cpptools/issues/12428) * Fix warning notification showing when `C_Cpp.getIncludes` is disabled. [PR #12470](https://www.github.com/microsoft/vscode-cpptools/pull/12470) * Fix a cause of colorization, inactive regions, and inlay hints getting cleared when an update is pending. * Update the default clang/gcc versions used for IntelliSense if an unknown version is found. * Fix a cause of semantic tokens transiently being placed in the wrong location. * Update clang-format and clang-tidy from 18.1.2 to 18.1.7 (for the bug fixes). * Fix a potential deadlock when configured using compile commands.

[sonarcloud[bot]]

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 SonarCloud

[github-actions[bot]]

Compressed layer size comparison

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

OS/Platform	Previous Size	Current Size	Delta
linux/amd64	432.86M	432.87M	17.34K (+0.00%)
linux/arm64	572.09M	572.11M	21.07K (+0.00%)

[github-actions[bot]]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	15		0	0.08s
✅ DOCKERFILE	hadolint	2		0	0.85s
✅ JSON	prettier	11	0	0	0.63s
✅ JSON	v8r	10		0	4.62s
✅ MARKDOWN	markdownlint	8	0	0	0.93s
✅ MARKDOWN	markdown-table-formatter	8	0	0	0.21s
✅ REPOSITORY	checkov	yes		no	14.96s
✅ REPOSITORY	gitleaks	yes		no	0.48s
✅ REPOSITORY	git_diff	yes		no	0.02s
✅ REPOSITORY	grype	yes		no	12.7s
✅ REPOSITORY	secretlint	yes		no	1.27s
✅ REPOSITORY	trivy	yes		no	5.9s
✅ REPOSITORY	trivy-sbom	yes		no	1.34s
✅ REPOSITORY	trufflehog	yes		no	4.16s
✅ SPELL	lychee	48		0	1.28s
✅ YAML	prettier	20	0	0	0.9s
✅ YAML	v8r	20		0	16.08s
✅ YAML	yamllint	20		0	0.47s

See detailed report in MegaLinter reports

_MegaLinter is graciously provided by _

[github-actions[bot]]

Compressed layer size comparison

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

OS/Platform	Previous Size	Current Size	Delta
linux/amd64	640.74M	640.77M	26.01K (+0.00%)
linux/arm64	633.10M	633.13M	21.83K (+0.00%)

[github-actions[bot]]

Test Results

 2 files  ±0   2 suites  ±0   52s :stopwatch: -1s 26 tests ±0  26 :white_check_mark: ±0  0 :zzz: ±0  0 :x: ±0  28 runs  ±0  28 :white_check_mark: ±0  0 :zzz: ±0  0 :x: ±0 

Results for commit d4ebbfdb. ± Comparison against base commit 9a86bfc1.

[github-actions[bot]]

Pull Request Report (#511)

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)	3.1 Hours
Time that was spend on the branch before the PR was created	1 Sec
Time that was spend on the branch before the PR was merged	3.1 Hours
Time to merge after last review	3.9 Min

Status check related measures

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

[github-actions[bot]]

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