Allow Token-Aware drivers for range scans

Currently, range scans are not token aware. This means that an extra hop is needed for most requests. Since range scans are usually data intensive, this causes significant extra traffic.

Token awareness could be enabled by having the coordinator return the token for the next (still unread) row in the response, so the driver can select a next coordinator that owns this row.