Optimize OTel Trace ID queries with skip index

[SpencerTorres]

Adds the optimization requested in #724

This optimization is only included in the SQL when OTel is enabled since the table is specific to OTel.

Here's the new SQL that is generated for Trace ID queries:

+ WITH
+ '207c6fb96eda8541559a283678587c86' as trace_id,
+ (SELECT min(Start) FROM "default"."otel_traces_trace_id_ts" WHERE TraceId = trace_id) as trace_start,
+ (SELECT max(End) + 1 FROM "default"."otel_traces_trace_id_ts" WHERE TraceId = trace_id) as trace_end
SELECT
"TraceId" as traceID, "SpanId" as spanID, "ParentSpanId" as parentSpanID, "ServiceName" as serviceName,
"SpanName" as operationName, "Timestamp" as startTime, multiply("Duration", 0.000001) as duration,
arrayMap(key -> map('key', key, 'value',"SpanAttributes"[key]), mapKeys("SpanAttributes")) as tags,
arrayMap(key -> map('key', key, 'value',"ResourceAttributes"[key]), mapKeys("ResourceAttributes")) as serviceTags
FROM "default"."otel_traces"
WHERE
- traceID = '207c6fb96eda8541559a283678587c86'
+ traceID = trace_id
+ AND startTime >= trace_start
+ AND startTime <= trace_end 
LIMIT 1000

Here's a rough graph of query duration before and after:

[asimpson]

LGTM 🎉

Just two nits, up to you on how you want to handle them 😎

[SpencerTorres]

Good points on the otel functions, pushed a change to clean up the imports/references 👌

[asimpson]

🏆 nicely done

[tanner-bruce]

FYI this query scans the trace_id_ts table twice.

Compare with:

(SELECT (min(start), max(end) + 1) FROM tracing.otel_traces_trace_id_ts WHERE trace_id = ID) as bounds,
...
AND startTime >= bounds.1
AND startTime <= bounds.2 

[SpencerTorres]

FYI this query scans the trace_id_ts table twice.

Very good point, this PR was simply using the linked query on the original issue, but this seems like another optimization we can add. Thanks!