Support process report
https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#progress
There's no real use for this at the moment as we do everything in a single thread. A good start could be to split out our build file compilation logic into a worker pool and use this for that.
Actually, this issue originated from:
Possibly during the first request, zls was not ready yet. In the previous design, the
LspProgressUpdateevent notification was used to trigger a second request. However, it appears that zls did not notify properly. https://github.com/zigtools/zls/blob/33121dacf9f7a178b40418840f5d66f9a9004992/src/Server.zig#L1423
Originally posted by @junnplus in https://github.com/junnplus/lsp-setup.nvim/issues/49#issuecomment-1563684632