Add revilowaldow.5etools-language-server

[Spappz]

• I have read the note above about PRs contributing or fixing extensions
• I have tried reaching out to the extension maintainers about publishing this extension to Open VSX (if not, please create an issue in the extension's repo using this template).
• This extension has an OSI-approved OSS license (we don't accept proprietary extensions in this repository)

Description

This PR adds the 5eTools Language Server; the developer has unfortunately been unresponsive.

License is MIT-0.

Thanks!

[filiptronicek]

Hi there @Spappz 👋 and thanks for your contribution. Could you please try raising an issue on the respective repo first? It seems that there were no issues yet and the extension is regularly being updates 🙏.

[Spappz]

I actually spoke with the developer directly and suggested publishing to Open VSX that way. I included a step-by-step process (both for doing it themselves or adding the module here) but, unfortunately, they were very clear that they had no intention of doing either ever. So, granted not 'unresponsive to contact', but it was certainly 'unresponsive to the proposition'!

I can raise the issue just for them to flag it down if you'd like the confirmation either way. ¯\_(ツ)_/¯

[revilowaldow]

Evening, as @Spappz indicates I have no interest in publishing to a second marketplace, however I’m happy for it to be automatically republished on my behalf through this method.

The whole thing feels very circular to me and I don’t want yet another account. Hypothetically the intent is to avoid telemetry, but we’re all using GitHub here; I’m publishing to the Microsoft marketplace, from vscode, on my windows pc. A core feature of the extension is to pull a schema (comprised of a hundred or so files) for data validation, directly from GitHub, which will definitely be tracking who’s requesting them from where how often etc. Then the first step of publishing an open vsx extension is to create an account, and immediately link that to GitHub. Then I have to accept a publisher agreement with a list of third parties you use, and then set up a PAT. And then every time I publish I’ve got to do all the admin twice, or do a load of up front CI pipeline work for which I do not care.

Again, I’m happy for the extension to be republished on my behalf, however I will not be creating an account.

[Spappz]

Hi, is there anything else to be done here before merge? A couple others and I are eager to see it in the repo given Revilowaldow's position above 😁

[filiptronicek]

Thank you @Spappz for the context. I am happy to have the extension on Open VSX, where it should land sometime tomorrow.