Code analysis should forward `-target` to clang

Feature Request

I have a codebase for an ARM Cortex M target, in which I use the arm-none-eabi-gcc compiler. I'm using this extension in combination with another extension that uses the API to pass compile commands to the C/C++ extension. This extension passes the compilerPath in both its provideConfigurations and provideBrowseConfiguration hooks.

As far as I can tell, intellisense is able to pick up on this and treat types like size_t as a 32 bit unsigned integer. Code analysis, however does not do this on its own. I can work around this by passing my compiler to clang through the code analysis arguments:

"C_Cpp.codeAnalysis.clangTidy.args": [
  "--extra-arg=--target=arm-none-eabi-gcc"
],

Could the code analysis engine pick up -target from the compilerPath automatically? I assume the same applies to raw compile_commands.json too.

Related to, but separate from #9829.

Trace how compilerPath is passed through provideConfigurations and provideBrowseConfiguration into code analysis, then compare that path with raw compile_commands.json handling. Confirm that the target is forwarded to clang automatically for both sources, including the ARM Cortex M case, without requiring C_Cpp.codeAnalysis.clangTidy.args.