[Dan (dpt-kw)]

This change addresses item #5069.

This adds support for CMake's SARIF files by adding extension settings which control generation of the file and whether contents are loaded.

The following changes are proposed:

• SARIF generation is controlled through the new setting exportSarifFile which will enable the cache variable CMAKE_EXPORT_SARIF unless the selected kit or preset specifies a value. Support was first added to CMake in 4.0.
• Loading language diagnostics is controlled by loadSarifFile. If enabled, the extension checks the SARIF status by checking both the cache definition CMAKE_EXPORT_SARIF and the CLI flag --sarif-output=.... If the file is modern, language diagnostics will be loaded from this file instead of the stream parser. Proper configure diagnostics support isn't available until CMake 4.5.
  • The SARIF parser avoids a couple issues that appear with the stream parser in newer versions of CMake (since the 4.4 diagnostics overhaul), like missing the message severity level and defaulting to error (e.g. AUTHOR_WARNING).

The purpose of this change

Add extension options for controlling the new CMake SARIF feature in VS Code. Allow CMake-language diagnostics to be loaded from the SARIF file.

[Dan (dpt-kw)]

@microsoft-github-policy-service agree company="Kitware, Inc."

[Dan (dpt-kw)]

I'm proposing adding a new dev-only dependency, @types/sarif@^2.1.7, which provides type definitions for SARIF. I'll need help from the team to add this dependency and otherwise review these changes. Is there someone specific I should ping?

CC: Hannia Valera (@hanniavalera)