cassandra.storage: Use next token for pagination instead of computing it

The existing implementation computed the next token using the tok (adding 1).
It's not good enough as it would skip some contents in case of collision on
tok (collisions exist as the tok here is a noncryptographic hash on 32 bits).

Related to T2518