[Feature] Use SARIF file to ingest CMake configure diagnostics

### Request Overview

The extension ingests diagnostics from CMake using stdout/stderr and a custom parser. CMake now supports generation of a [SARIF](https://sarifweb.azurewebsites.net/) log file during configuration. The CMake Tools implementation would be less fragile if configuration diagnostics were imported from the SARIF file. This also positions the extension to add richer metadata to diagnostic reporting as the CMake SARIF feature is developed.

Right now, CMake only provides configuration diagnostics over SARIF, so that's the scope of this request. General output logging and other modes are out of scope, but there is active discussion/plan formulation for supporting SARIF logging in other CMake modes too.

### Additional Information

_No response_

Start by locating the CMake configuration diagnostic flow that reads stdout/stderr and uses the custom parser. Review how CMake generates SARIF during configuration and how diagnostics are passed into the extension. Done means configuration diagnostics are imported from SARIF while general output logging and other CMake modes remain out of scope.

Written by the indexing model from the issue text.