CMake: Compile Active File command should rely on cmake-file-api instead of compile_commands.json

### How CMake: Compile Active File works

From the discussion in issue #2180 (now closed), it appears that the CMake: Compile Active File command only works if the `compile_commands.json` file is exported and made available somewhere. However, this poses a limitation, since the only two CMake generators supporting the export of the compile commands file are Makefile and Ninja (Ninja Multi-Config exports one compile commands file with all configurations mixed up and therefore is unusable, though this seems a problem of CMake itself, not this extension).

### Using cmake-file-api

As far as I've understood, [cmake-file-api](https://cmake.org/cmake/help/latest/manual/cmake-file-api.7.html) exposes all the information needed to compile and build targets and even single files for any generator (even Visual Studio or Ninja Multi-Config). Relying on this instead of compile commands file should make Compile Active File always work independently from the platform or generator.

Would it be possible/make sense to make this modification? After all, interaction with file APIs is already implemented in this extension as from setting `cmake.cmakeCommunicationMode` and I suppose that is how targets are built from the CMake Project Outline in the Primary Side Bar.

Start by tracing the CMake: Compile Active File command and compare its current compile_commands.json dependency with the existing cmake.cmakeCommunicationMode and CMake Project Outline file-API interactions. Read the cmake-file-api documentation to determine how generator- and configuration-specific compile information could replace the current source, then verify that the command works across the generators described in the issue.

Written by the indexing model from the issue text.