Variable statement positions incorrect - cutting short

[scatternoodle]

Two sub-issues to this one:

• [ ] Make VariableStatements include terminating semicolon
• [ ] Add 1 to end of range - for now just within the documentSymbolsProvider code because I don't think this is a "thing" for ranges in all contexts.

[scatternoodle]

There's two problems here.

1. The VariableStatements are not including the semicolon, I think we want to bring those in. Otherwise, it's cut off in the token and if you e.g. select the whole thing and delete it you're left with the semicolon afterward.
2. The start of ranges in VSCode is interpreted correctly as zero-indexed, but the end is getting pushed back one place... it's a little weird - it's like it's zero-indexed for the start of the range, but 1-indexed for the end - so we have to +1 at the end. This only seems to happen for documentSymbols though, because this wasn't happening with semantic tokens!