cmake tools kits scan when update a kit in the same path it won't update the json file correctly

Brief Issue Summary

for e.g. installing GCC 13.2 with mingw

using it with VS code (running scan for kits)

then upgrading to GCC 14.2

running again scan for kits.

the result is there are 2 kits pointing at the same path. The latter is correct.

So the error is scan for kits function doesn't update/replace (or simply remove older entries) when a new kit is discovered that has the same path of something that is already present in the list (or in the cmake-tools-kits.json file).

detailed e.g. with cmake-tools-kits.json

{
    "name": "GCC 13.2.0 x86_64-w64-mingw32 (ucrt64)",
    "compilers": {
      "C": "C:\\msys64\\ucrt64\\bin\\gcc.exe",
      "CXX": "C:\\msys64\\ucrt64\\bin\\g++.exe"
    },
    "isTrusted": true,
    "environmentVariables": {
      "CMT_MINGW_PATH": "C:\\msys64\\ucrt64\\bin",
      "MSYSTEM": "UCRT64",
      "MSYSTEM_PREFIX": "/ucrt64",
      "PATH": "C:\\msys64\\ucrt64\\bin;C:\\msys64\\usr\\bin;${env:PATH}"
    },
    "preferredGenerator": {
      "name": "MinGW Makefiles"
    }
  },
  {
    "name": "GCC 14.2.0 x86_64-w64-mingw32 (ucrt64)",
    "compilers": {
      "C": "C:\\msys64\\ucrt64\\bin\\gcc.exe",
      "CXX": "C:\\msys64\\ucrt64\\bin\\g++.exe"
    },
    "isTrusted": true,
    "environmentVariables": {
      "CMT_MINGW_PATH": "C:\\msys64\\ucrt64\\bin",
      "MSYSTEM": "UCRT64",
      "MSYSTEM_PREFIX": "/ucrt64",
      "PATH": "C:\\msys64\\ucrt64\\bin;C:\\msys64\\usr\\bin;${env:PATH}"
    },
    "preferredGenerator": {
      "name": "MinGW Makefiles"
    }
  }

as you can see it is obliviously an error having the same compilers PATH but 2 different kits

"GCC 13.2.0 x86_64-w64-mingw32 (ucrt64)" ===>"compilers": { "C": "C:\msys64\ucrt64\bin\gcc.exe", "CXX": "C:\msys64\ucrt64\bin\g++.exe" }
"GCC 14.2.0 x86_64-w64-mingw32 (ucrt64)" ===> "compilers": { "C": "C:\msys64\ucrt64\bin\gcc.exe", "CXX": "C:\msys64\ucrt64\bin\g++.exe" }

NOTE: in this specific case even the PATH is the same.

CMake Tools Diagnostics

No response

Debug Log

No response

Additional Information

this is an error on the internal data design, it should something unique, like the full path of the compiler exe. Understand it might be tricky when there are multiple compilers, but for sure when all the compilers are matching another kit, it can be considered a duplicate, like the example above.

Furthermore it could even do a 2nd level comparison on the enviromentalVariable if also those 2 are the same.. ... well the only thing change most likely is only the name.

in this specific e.g. should have just update the kit's name as the final result.

microsoft / vscode-cmake-tools