Tracing: use pagination for queries fetching a huge number of spans

[guilload]

I have implemented streaming spans ordered by trace ID in batches of size 1,000. However, regarding memory consumption, all the spans are still held in memory because we don't have a streaming search endpoint that allows sorting by a field (yet). An alternative solution would be to use pagination.