feat: set up `npm publish` for standalone server executable

[llllvvuu]

resolves #282

The only thing I didn't do is change the package.json name, since that would also change the VSCode extension name. But solidity is taken on NPM, so you'll need to temporarily change the name each time you run npm publish and then change it back. This can be done in a GitHub Action.

Publish to NPM: npm publish.

Users:

npm install -g @juanfranblanco/vscode-solidity-server
vscode-solidity-server --stdio

The changes:

• adds "files", "bin", and "prepublishOnly" to package.json to use tsup
• updates server.ts to read the default config from package.json so that even if the client doesn't send a config, they'll still get the default behavior. This is because if the non-VSCode client has to keep manually copying the client config from package.json, it's hard to keep it up-to-date.
• chore: remove unused packages so they don't get downloaded unnecessarily
• the big-looking diff in server.ts is just me moving the onDidChangeConfiguration logic into a separate function so that it can be run in both onInitialize and onDidChangeConfiguration.

[juanfranblanco]

Wow thanks this is great!

[llllvvuu]

@juanfranblanco did you want to set up an npm account? or I can publish an independent version

[PierrickGT]

@llllvvuu is there any guide available to set this up in Neovim?

[llllvvuu]

@llllvvuu is there any guide available to set this up in Neovim?

I forked nvim-lspconfig: https://github.com/llllvvuu/nvim-lspconfig/commit/08664bf761f73bc129df7f1cfb9b29884793ae81

I will make that a PR if/when the npm release becomes available from @juanfranblanco (https://github.com/juanfranblanco/vscode-solidity/pull/429)