[ES|QL] highlighting is incorrect when the error comes from the server

[drewdaemon]

Kibana version: 8.14

When a user submits a query and gets an error from Elasticsearch, we try to highlight the relevant bit. But, we often fail and the highlight shows up in seemingly-random places.

A couple of examples

from kibana_sample_data_logs | eval abs(@timestamp) | limit 10

from kibana_sample_data_logs | limit 23408239482038

[elasticmachine]

Pinging @elastic/kibana-esql (Team:ESQL)

[drewdaemon]

I was on the fence between impact:low and impact:medium. This bug doesn't prevent the user from seeing the message and figuring out what went wrong. But I could definitely see it being confusing...

[stratoula]

My guess here is that the error position is not being returned correctly from ES but we need to check. I havent encountered ever tbh so is def low