Allow paging through non-ordered partitioner results in CQL3

CQL < 3 silently turns a "key >= X" into "token(key) >= token(X)". This is not what users will expect, since many of the rows returned will not in fact satisfy the requested key inequality. We should add syntax that makes the difference between keys and tokens explicit, possibly with a token() "function" as imagined here.