setConfig api option to set only in memory

还没有人认领这个 Issue。

My extension dynamically generates a library bundle and sets a path in `userThirdParty` and `checkThirdParty: "ApplyInMemory"`, to allow the rest of my settings to be applied from the config.json, and library and plugin loaded, with minimal impact on the user's workspace. I currently set these two in the workspace via vscode settings apis, which leads to them being written to settings.json. Persisting these is undesirable as the `userThirdParty` path is a per-workspace path, which many users have complained about.

I noticed that the extension now provides a setConfig api, and was hoping to use this to provide those settings only in memory, but it seems they are also written back out to settings.json when set this way.

Would it be possible to have an "ApplyInMemory" option on the setConfig api for this case?

首先跟踪 setConfig API 和 VS Code 设置 API，以找出配置更改的持久化位置。当 ApplyInMemory 选项能够应用 userThirdParty 和 checkThirdParty，而不将它们写入 settings.json 时，即视为完成；该 issue 未指定文件或测试，因此必须先确定相关的实现路径和验证路径。

由索引模型根据 Issue 内容生成。