removing limit + migrating n_return -> batch_size

We weren't really handling limit correctly (weren't converting it to
$maxScan for queries, interchanging it with batch_size randomly).  Just
removed it for now.

Also, changed n_return to batch_size, which more clearly indicates what
it does.

For limit behavior in queries (outside of counts), we'll rely on directly
including $maxScan