Timepicker running a query with every change

[AlonaNadler]

Describe the feature: create a setting that changes in the timepicker will not trigger queries, queries will run only if users explicitly run them

Describe a specific use case for the feature: currently when users change the time range via the timepicker it triggers a query, it creates unwanted queries which in a large cluster can slow down the cluster. e.g user in Discover change the timepicker to the last 30 days, before creating the query in the search bar, by changing the time range it immediately creates an empty query on the last 30 days, which is a very intensive query

[AlonaNadler]

This issue was requested by a customer, I understand why it can be a pain point, running undesired queries with every change of the timerange.
I would rather us focus on terminating queries once running (http://www.github.com/elastic/kibana/issues/17845) since I think it will solve a bigger use case

[timroes]

We discussed this yesterday and came to the conclusion, that this feature is just a fallout from not being able to properly cancel running requests (either automatically when chancing context #17845, or manually via the UI: #17265). So we'll be closing this in favor of canceling requests.