explorev2/stores/controls: use default time range

[vavrusa]

The reasoning is that most of the controls use first available value.
7 days is really impractical for huge datasets where it can easily be
petabytes of data, so it makes initial load slow.

[mistercrunch]

Might as well hard code '1 hour ago' as choices is static.

1 hour ago is probably impractical as well for batch data of tables loaded daily. Arguably 7 days is a decent default for batch data and 1 hour is decent for realtime data.

The default from time filter could be set at the datasource level, but I doubt people would take the time to alter that configuration setting.

[vavrusa]

So arguably neither of them works for all use cases, so what would you prefer we do?

• Make it configurable in the datasource
• Do not immediately launch a query as soon as the explore view is opened

For (b) the default wouldn't then matter as the time range is the first thing I change when I open the explore. This is actually one of the most annoying things, it launches query before even giving me a chance to provide any input in the form.

[mistercrunch]

Closing old PRs with broken build or merge conflict, feel free to re-open once merge conflicts are sorted out.