Create VS Code extension using LSP server

[mark-wiemer]

We can rework the existing Luanti Tools extension with @GreenXenith's permission or make a new official one. This extension should use LSP to ensure the core logic can be extended to other IDEs as needed.

Pre-reqs: #313

[GreenXenith]

This depends on having a consistent source for an LSP to pull from, no sense discussing it right now.

For later consideration: Fragmenting ecosystems is generally bad, so on one hand I would prefer integrating an LSP with my extension. It already planned for this anyway. On the other, a new extension would let us rename the extension (because Microsoft doesn't know how to rename things, apparently), and potentially put it under the Luanti org.

[mark-wiemer]

1. No need to discuss it now, just wanted to clearly put it on the backlog
2. You can rename existing VS Code extensions, I did it with AHK++, but you can't change the ID. That said, I think "Luanti Tools" is a fine name for an official extension anyway.
3. We can transfer ownership of the extension to the Luanti org as needed, that is a bit of paperwork that I'd have to look up, but it's been done before with a pretty good end-user experience.

[GreenXenith]

Thats what I meant, I cant change the ID. Underneath its still minetest-tools. If we make a new one, it is an opportunity to change the ID.