[Feature]: Implement max trace size parameter in the query service

[yurishkuro]

Requirement

For background see #1051 (comment)

Problem

Even though Storage V2 API supports streaming of the span data from storage, the query service still has to buffer everything in order to apply query-time adjustments (such as clock skew fixes) which require the full trace. This exposes the query service to OOMs if the trace has too many spans.

Proposal

• Add a parameter to query service for the max trace size
• Only load spans from storage up to that amount
• If the load is aborted, add a warning to the returned trace indicating that not all data was loaded

Open questions

No response

[tdn21]

@yurishkuro i'd be happy to work on this, could you please assign it to me? Thank you! 🙇

[AnmolxSingh]

@ADITYATIWARI342005 are you still working on this issue?

[ADITYATIWARI342005]

@AnmolxSingh the Pull Request has passed most of the reviews, there are some reviews to be addressed.
You may refer the Linked PR #7499 for more information.
The issue may be closed in few hours, as I make final changes as per review.
Thank you for your concern.