`WorkspaceBrowseConfiguration` should support multiple sets of compiler path/args

If I understand correctly, it’s not uncommon for CMake projects to consist of several subprojects that could use different relevant args or hypothetically even different compilers (i.e. target binaries vs. tools built for the host system to be used by the build).

There is also the need for C vs. C++ information, as compiler queries for either may result in different system include paths.

Processing N sets of compiler paths/args here would be similar to what cpptools does with compile_commands.json files - processes all provided compiler paths and (unique and relevant combinations of) args, to build the browse path(s). Cpptools should be able to avoid redundantly querying compilers, so it should not be critical that the configuration provider de-dupe this set.

Commencez par lire la WorkspaceBrowseConfiguration API et examinez comment cpptools traite compile_commands.json, comme décrit dans l’issue. Définissez et documentez la prise en charge de plusieurs ensembles de chemins/arguments de compilateur, y compris des requêtes distinctes pour C et C++ ; le travail est terminé lorsque l’API peut représenter ces ensembles pour les sous-projets sans nécessiter de requêtes redondantes au compilateur.