[Logs UI] Correctly round and update the log stream end timestamps

[weltenwort]

📝 Summary

This fixes the handling of the end timestamp in the log stream page query state machine.

closes #152363
closes #152337

🕵️‍♀️ Review notes

• This fixes two problems that depend on each other:
  1. When evaluating an end time value containing date math, properly round it up.
  2. When refreshing the end timestamp upon reaching the bottom of the stream, it now preserves the time range instead of forcing a now as the end time value.
• This also fixes the visual layout of the position state machine and moves the throttling delay to the configuration so the after transition is properly recognized by the visual editor:
  

[weltenwort]

@elasticmachine merge upstream

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 8f7c8ba

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
infra	1.3MB	1.3MB	+73.0B

Unknown metric groups

ESLint disabled line counts

id	before	after	diff
securitySolution	428	430	+2

Total ESLint disabled count

id	before	after	diff
securitySolution	506	508	+2

History

• 💔 Build #111176 failed 7e648d1

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

cc @weltenwort

[elasticmachine]

Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI)

[tonyghiani]

LGTM, I tested locally the scenarios I found broken and everything works fine now, thanks for taking on this so quickly 👏

[kibanamachine]

💔 All backports failed

Status	Branch	Result
❌	8.7	Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 152387

Questions ?

Please refer to the Backport tool documentation

[weltenwort]

The code containing the bug doesn't exist yet in 8.7, so I'll abort the backport.