[Timelion] Better error details on expression evaluation

[dej611]

Summary

Fixes (partially) #107399
This is a first part of the fix for the linked issue: now the server can send more details about the error due to expression evaluation and the client can show it.

Next step should be probably to provide better error messages from the server side.

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: e82616a
• Storybooks Preview

Metrics [docs]

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
visTypeTimelion	10.2KB	10.3KB	+19.0B

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[elasticmachine]

Pinging @elastic/kibana-vis-editors (Team:VisEditors)

[stratoula]

Yes this is a great improvement from the previous state. For example when the interval is so small, now the error message makes more sense than the previous generic one. I agree that also the server errors could be improved but still I find it a very good enhancement :)

LGTM! Thanx Marco :)

[kibanamachine]

💔 Backport failed

The backport operation could not be completed due to the following error:
Unexpected response from Github API (v4):
{
"message": "We had issues producing the response to your request. Sorry about that. Please try resubmitting your request and contact us if the problem persists."
}

The backport PRs will be merged automatically after passing CI.

To backport manually run:
node scripts/backport --pr 112663