transport: route non-default keyspace queries properly

[Kulezi]

Right now in the case of a token aware query on a keyspace other than default, it will use the plan for the default keyspace.
Those queries should follow the plan described in the keyspace, could cost a few allocations as queries on non-default keyspaces should be quite rare.