[Security Solution][Timeline] - fix host and user details flyout not using the correct time for requests when open from Timeline

[PhilippeOberti]

Summary

This PR fixes a bug in the user and host detail flyouts (the new ones using the expandable flyout framework). When those flyouts are open from Timeline, the request made to query their data is using the from and to values from the global query, meaning the date interval selected in the alerts page. They should be instead using the date interval from Timeline.

Before fix

https://github.com/elastic/kibana/assets/17276605/84685de8-402d-4dc9-85e9-3e78f50e520f

After fix

https://github.com/elastic/kibana/assets/17276605/ad365303-f0a9-4a90-9e46-8bd742df8db6

https://github.com/elastic/kibana/issues/182967

Notes

I did not add any unit tests for this, as the cutoff for the last BC is happening very soon, and also because no tests existed for these 2 hooks. Let me know if that is ok with you for now @machadoum

[elasticmachine]

Pinging @elastic/security-threat-hunting-investigations (Team:Threat Hunting:Investigations)

[elasticmachine]

Pinging @elastic/security-entity-analytics (Team:Entity Analytics)

[kibana-ci]

:yellow_heart: Build succeeded, but was flaky

• Buildkite Build
• Commit: c55a87e537d02fd60eaa4fdf0dd8f1266c1a72e1

Failed CI Steps

• FTR Configs #72

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
securitySolution	15.3MB	15.3MB	+340.0B

History

• :broken_heart: Build #208720 failed c7ff516beb5e699d277290df1c186deebcd40fa0

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

[kibanamachine]

💚 All backports created successfully

Status	Branch	Result
✅	8.14

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation