Specific files.exclude breaks file scanning workspace.library

Which OS are you using?

Windows

Expected Behaviour

When I specify the complicated mask of editor's files.exclude ugh... because there is no other way https://github.com/microsoft/vscode/issues/869

		"files.exclude": {
			"**/?*.[!l]*": true,
			"**/?*.l[!u]*": true,
			"**/?*.lu[!a]*": true,
			"**/?*.lua?*": true
		},

I expect to exclude all files from the VS Code project except .lua, so this should not affect the plugin in any way.

Actual Behaviour

I see that LuaLS file scanning is starting to work incorrectly, it may selectively skip my libraries from Lua.workspace.library list.

Reproduction steps

1. Setup Multi-root Workspaces project https://code.visualstudio.com/docs/editor/multi-root-workspaces
   for example our file located in proj/data/game/.vscode

	// relative to proj/data/game/.vscode
	"folders": [
		{
			"path": ".." // proj/data/game
		},
		{
			"path": "../../scripts" // proj/data/scripts
		},
		{
			"name": "system_data/game",
			"path": "../../../system_data/game" // proj/system_data/game
		},
		{
			"name": "system_data/scripts",
			"path": "../../../system_data/scripts" // proj/system_data/scripts
		}
	],

2. Setup Lua.workspace.library for correct Multi-root Workspaces file scanning

		"Lua.workspace.library": [
			"../../data/game",
			"../../data/scripts",
			"../../system_data/game",
			"../../system_data/scripts",
			".vscode/library" // some meta definitions in `proj/data/game/.vscode`
		],

3. Everything works fine. Then setup editor's files mask

		"files.exclude": {
			"**/?*.[!l]*": true,
			"**/?*.l[!u]*": true,
			"**/?*.lu[!a]*": true,
			"**/?*.lua?*": true
		},

4. Now some annotations are missing or the files just haven't been loaded.

Additional Notes

No response

Log

No response

Reproduza o cenário de Workspace multi-root do Windows usando as configurações mostradas de files.exclude e Lua.workspace.library. Comece rastreando o caminho de varredura dos arquivos do Workspace na extensão do VS Code e compare os resultados com e sem files.exclude. Considera-se concluído quando todos os caminhos de biblioteca configurados forem verificados de forma consistente e as anotações ausentes ou os arquivos não carregados não ocorrerem mais.