Include flags with relative directories always resolve relative to workspace

Problem

If a SourceFileConfiguration includes a entry in compilerFragments like /I..\foo, cpptools will attempt to resolve that include directory relative to the VS Code workspace root and silently discard the flag if the directory does not exist. However, it's possible that the compiler process was invoked with a different working directory than the workspace root, and the relative include directory would have resolved successfully relative to the compiler's working directory.

Suggested fix

Add a new readonly directory?: string; property to SourceFileConfiguration that specifies the working directory of the compiler process. Relative paths in compilerFragments should resolve relative to directory, if it is defined.

まず、SourceFileConfiguration の宣言と、VS Code ワークスペースのルートを基準に compilerFragments を解決するコードを見つけます。コンパイラーの作業ディレクトリがどのように表現されているかを確認し、相対インクルードパスに定義済みのディレクトリが使用されること、また新しいオプションのプロパティが公開 API に公開されることを確認します。