Register function environment variables

まだ誰も着手していません。

This extension is able to detect usage of undefined global variables:

However, `setfenv` is used on this function to define the missing variable, but at another point in the code that the parser can't detect. Is it possible to somehow tell the parser to ignore this diagnostic? Something like:
```lua
local block = function(_)
-- env: {block, assert, error}
block()
end
```

Then it would accept those values? I know you can define globals for the project, but this doesn't affect the entire project, only those functions, so it would be cool if you could define it somehow.

Alternatively, could we just disable the diagnostic?
```lua
local block = function(_)
-- disable: undefined-global
block()
end
```

I don't know if the parser supports reading comments like that, let me know if that won't work or if you have better ideas for it.

まず、parser の未定義グローバル診断を追跡し、プロジェクトレベルのグローバル定義をどのように読み取るかを調べます。次に、issue で提案されている関数ローカル環境のアノテーションと診断を無効化するコメントを評価し、選択した構文が意図した関数スコープの警告だけを抑制または解決することを確認します。

索引モデルが issue の本文から書いたものです。