[Feature-Request/Question] Hide diagnostics while keeping require definitions for project files

I have a project, where I use luarocks with modules directly installed in the projects folder (similar to how npm does it), which is handy for adding require paths, however what should I do, if they raise warnings?

I tried the following:

{
	"Lua.runtime.version": "LuaJIT",
	"Lua.workspace.library": [
		"${3rd}/love2d/library",
		"${3rd}/lfs/library",
		"${workspaceFolder}/lua_modules"
	],
	"Lua.runtime.path": [
		"src/?.lua",
		"src/?/init.lua",
		"doc/?.lua",
		"${workspaceFolder}/share/lua/5.1/?.lua",
		"${workspaceFolder}/share/lua/5.1/?/init.lua"
	],
	"Lua.workspace.ignoreDir": [
		"extern",
		"lua_modules" // Need option to ignore diagnostics, but keep definitions
	],
	"Lua.diagnostics.libraryFiles": "Disable",
}

首先检查 Lua.workspace.ignoreDir 和 Lua.diagnostics.libraryFiles 的处理方式，以 issue 中显示的配置作为切入点。跟踪 lua_modules 如何从诊断中排除，以及如何仍然为 require 路径发现其中的定义。完成的标准是：项目本地模块仍可用于定义，同时抑制其警告；issue 中未指定任何文件或测试。