storage.cassandra: Improve content_get_partition pagination implementation

As per remark [1] inlined here.

tok+1 is not good, it would skip some contents in case of collision on tok. (And collisions do happen, it's a noncryptographic hash on 32 bits.)

We should instead use the token of the next token. It will return the same contents twice though; but that's less of an issue.