[Feature]: Need support for pagination in api/v3/traces endpoint

Requirement

As a Jaeger API consumer migrating from Jaeger v1 to Jaeger v2, I want the /api/traces endpoint to support the offset query parameter, so that I can paginate through trace search results and maintain compatibility with applications currently using Jaeger v1.

Problem

Our application currently uses the Jaeger v1 API:

GET /api/traces ?service={serviceName} &operation={operationName} &tags={} &start={startMicros} &end={endMicros} &limit=20 &offset={offset}

The application relies on offset to retrieve subsequent pages of trace results.

Proposal

No response

Open questions

Is offset pagination planned/supported for the v3/api/traces API, or is there a recommended alternative for applications that require offset-based pagination?