BETWEEN, a more mature approach

This is a work in progress.

`RANGE` is now compiled to construct an array of values.

`Between` is now handled as follows in the planner phases:
1. an `ExprOp` is constructed, but not yet used (not the correct one yet; there will be some work to represent all the expressions we support as exprOps, but I believe everything is in place to do this work). This expression will eventually be used to translate portions of the expression to JS for use with `$where`.
2. a `Selector.And` instance is constructed which is actually used.
3. the pipeline phase has a case for `Between` so as not to fail, but does nothing interesting with it. Not sure what we actually need there, if anything.
Well, it can merge the arguments, but in general that's not the right thing to do, so it just fails fast.

If we are generating an expr op for the case, you won't need to do anything, because the pipeline phase will say, "Oh, this has an expr op, I don't need to worry about generating a pipeline." The lack of an expr op is a sign that pipeline phase has to kick in (or fail trying).