Users selection to allow queries to run beyond configurable timeout

[AlonaNadler]

This suggestion was discussed on EAH,
Occasionally, users can run queries that might take longer time, provide a popup after a configurable time (or at timeout) that notify the query takes longer, users can decide whether they want to continue waiting for the results or to refine the query, which will cancel the running query and let the user refine the search, time range or aggregation.
This can also improve the experience when using frozen indices, where queries might take longer and likely reach timeout. Based on the users' decision the query can continue running beyond the configured timeout.

An example that might apply for Discover

[elasticmachine]

Pinging @elastic/kibana-app-arch

[stacey-gammon]

How would this work on dashboard when each embeddable is executing it's own query? Would they be saying "cancel this query" so I can change it at the dashboard level? Or would the user be saying "cancel all queries", so I can then change the time range at the dashboard level? Or would the user be saying "cancel this embeddables query, and then change the query for this embeddable only"?

Would they get a pop up for every embeddable on the dashboard?

[lukasolson]

Just leaving a note here that the first phase of this is planned to allow a user, while still on a page, to wait & allow the query to continue running (using ES async_search APIs). See elastic/elasticsearch#49931 & #53538.

[lukasolson]

Closed by #60706.