Ignore responses for previous query when filter/query has changed

[tylersmalley]

When querying data, it's possible for us to receive out of order responses. Take the following example; when an expensive query (A) is issued, the filter is updated resulting in query (B) - B can return before A, but A will be the last result to render.

This is more low-hanging fruit mentioned in #17844 (comment). In that issue it describes canceling the query using the ES tasks API. I feel that simply ignoring the canceled response is a good first step in improving this use case.

[dmlemeshko]

I see similar problem with TSVB (master) while running automated tests in Firefox (geckodriver):

After quick navigation from Times Series tab, the Metric tab still shows TImes Series data: probably because request made on 1st tab was not cancelled and it was finalized when 2nd tab is already displayed.