Syntax highlighting incorrectly highlights quoted string in command

[fmoo]

Repro case:

title: InitGlobal
---
<<TODO "Initialize anything">>
===

produces the following:

This is on version 2.0, released on 12/18

[McJones]

I had a hunch as to this and it turned out to be correct. Not sure what the best fix should be at this stage but writing this down so I don't forget the cause.

The issue is in SemanticTokenVisitor.cs SplitCommandText function in the LSP.
That correctly identifies in the above example there are two tokens TODO and Initialize anything but because that splitting code is dropping the the "'s at either end (because its mostly the correct thing to do) the range of the token is off by two.
This is where the trick is, by default the extension will use a basic syntax highlighter that will see "Initialize anything" as a String later the LSP runs and goes "yeah nah that isn't a string its a parameter" which is correct but because the LSPs tokens are two shorter the last two characters are still using their initial "I am a string" settings they got from the first syntax highlight pass.

I suppose can just add the "'s back in but I would have to check if that causes issues with other parts of the LSP that check the validity of commands.