Adapt to typescript-plugin approach

[rchl]

New version of Vue Language Tools is implemented using a typescript plugin rather than standalone server. We should support that approach.

(We shouldn't need to rush since it will take some time for it to iron out new issues)

Some ways of handling it: 1) Let user use LSP-typescript and manually set up the plugin per project 2) Bundle VLT plugin with LSP-typescript 3) Support some way of auto-registering plugins with LSP-typescript so that it's possible for this package to register the plugin automatically when installed. (Q: will it be OK to enable the plugin even for non-vue projects or could it cause issues?) 4) Like 3 but using a separate "LSP-typescript-vue-plugin" package (or whatever would be the appropriate name)

[niksy]

Is there any ETA when can we expect this?

It seems like issue with changes in related files is fixed with TS plugin approach.

[rchl]

I don't have time to work on that at the moment. Maybe in few months. But my current thinking is that it should:

• be a separate package like LSP-typescript-vue maybe to make it clear that it's a plugin to LSP-typescript
• not activate unless opted-in (how opt-in should work is to be determined)