Search aggregation insights do not allow to trigger explicit aggregation when timeout was hit
Created by: felixfbecker
In the case of the short 2s timeout being hit, the RFC states it should still be possible to trigger an explicit aggregation by clicking one of the buttons. This should cause the aggregation to re-run without a timeout.
In the state that the timeout was hit, simply only the buttons should be shown (no explicit error message).
Essentially, when a timeout is hit, the behavior and UI reacts the same as when proactive insights were disabled through the feature flag.
Currently, an error message is shown, the buttons are disabled, and there is no way to override the timeout.
/cc @joelkw @felixfbecker @vovakulikov @unclejustin