Web console doesn't always highlight correct error position

[bziobrowski]

Describe the bug

For some SQLs web console doesn't mark proper error position returned by backend .

To reproduce

1. Open web console
2. Execute
   select * from long_sequence(1) where cast(x as timestamp) = '2012-04-12T12:00:0A'
3. Check that error marker is at start of line

Expected Behavior

Web console should mark problmatic timestamp literal - either whole or start or end.

Environment

- **QuestDB version**: latest 6.2.1 master
- **OS**: Windows
- **Browser**: Chrome

Additional context

No response

[hezean]

A guess: the problem was caused by monaco-editor API's getWordAtPosition, which cuts the word '2012-04-12T12:00:0A' on the first dash.

Another example:

https://github.com/questdb/questdb/blob/37432fc6090de1d882ca278d365924f1a488e530/ui/src/scenes/Editor/Monaco/utils.ts#L217-L224

Could anyone kindly point out the next step? I'm not familiar with monaco -- maybe there are other APIs, or may set - as escaped from splitting.

[argshook]

Also reported here: #71