Support a file blacklist in tsserver configuration options

My scenario is this: suppose I'm working in my editor, and I open a file which, by chance, crashes the language service. Repeatedly. (usually because of it's size or shape). Today, after the service crashes 5 times in short order, the service is disabled by the editor (which if it crashes on load, is what will occur). What I propose is this; if the service crashes after a file open request is issued, and we would shut down the service, instead we automatically add the file to a workspace-local tsserver blacklist config (probably in .vscode/settings.json) and reload the language service with the new option. The language service will then refuse to actually load the blacklisted file contents, instead reporting them as empty files/empty modules/empty json documents and potentially issue a warning-type error message in the diagnostics that certain files are blacklisted, which may affect the compilation.

cc @mjbvz do you think this'd be a good idea for a slightly more progressive degradation of experience when the language service has trouble with a file?

まず、tsserver による file-open requests の処理と、language service が使用する構成オプションを追跡します。workspace ローカルの .vscode/settings.json で blacklist をどのように表現できるか、またクラッシュが繰り返された後に reloads がどのように発生するかを確認します。blacklist に登録されたファイルが安全に空として扱われ、diagnostics でその影響を警告でき、サービスが無効化されるのではなく利用可能なままになることが完了条件です。