[VSCode client] Extension appears to be ignoring workspace-level `runBuildScripts` setting

Repro

1. Create or git clone a Rust project which includes a build script (I'm currently seeing the issue in rust-skia)
2. (optional) For easier identification of the issue, force a build script to fail by explicitly panicing
3. In VSCode > Settings > User tab, ensure the setting Rust-analyzer > Cargo: Run Build Scripts is enabled
4. Create a new file in the test workspace at .vscode/settings.json with the following content:

   {
     "rust-analyzer.cargo.runBuildScripts": false,
     "rust-analyzer.procMacro.enable": false
   }
   

5. If necessary, run cargo clean at the workspace root and re-open VS Code with the RA extension enabled

Actual Behavior

• The rust-analyzer indicator in the status bar eventually displays a "Warning" icon
• View > Output > Rust Analyzer Language Server displays something like the following output:

  [ERROR rust_analyzer::reload] failed to switch build data: rust-analyzer failed to run build scripts:
  ...
  

Expected

Rust Analyzer extension should respect the workspace-level cargo.runBuildScripts setting and forgo executing build scripts if the option is disabled.

Notes

Please let me know if there's something I'm missing / some other explanation for the behavior I'm seeing.

Reproduce the issue in a VS Code workspace using the reported Rust project setup, enabling the user setting and disabling rust-analyzer.cargo.runBuildScripts in .vscode/settings.json. Trace how the VS Code client reads workspace configuration and verify that the workspace value is applied; done means build scripts are not executed and the Rust Analyzer output no longer reports their failure.