Add time range extraction and interval grouping support to execution engine.

## Overview

This pull request adds support for extracting the time range from an expression and then applying that to the interval synchronization within the processors. tl;dr the start and (optionally) end time range of the query is extracted and used for the iterators passed to each mapper so they can emit values on the same intervals (even if there aren't actually data points in those intervals).

## Example

This PR includes support for interval group by statements with a time range:

```
SELECT sum(value)
FROM cpu
WHERE time >= now() - 3h AND time < now()
GROUP BY time(30m)
```

## Notes

There will be more changes once full group by support is added (e.g. n-number of tag dimensions).

I moved some notes I made with Paul to the `NOTES` file. I'll remove it once the execution engine is done. Don't bother reading through it. It won't make any sense. :)
OK, if I understand correctly, if someone has this query:

`time > 100`

this means we have no upper bound. But this is getting signalled with `0` time for that bound. But then how does the code handle a situation where a user sets an explicit upper bound of 0? I mention this below. I know it would be pretty pointless, but how do plan to handle it?