fix(lsp): properly handle encoding URLs from lsp client

[kitsonk]

Fixes #9741

[lucacasonato]

LGTM. It's kind of worrying that we are binding so close to JS because VSCode is the dominant editor.

[kitsonk]

It's kind of worrying that we are binding so close to JS because VSCode is the dominant editor.

This should work for any editor though, it just widens the situation where the URLs can be "manipulated" by a client, but still have the LSP work properly, versus specifically coupling to VSCode. This should be opaque to other editors.