[EPIC] Make the trace-explorer page more useful

[ankitnayan]

• Poor perf of traces tab in the trace-explorer page #5861
• Allow filtering RootSpans, serviceEntry spans, any span Filtering on whole traces instead of root spans in Traces Tab in trace explorer #6013, show users rootSpan where one of the spans satisfies the where clause (Eg, db.system='mysql') #3085
• Filter traces with span count > x #3174
• https://github.com/SigNoz/engineering-pod/issues/1755
• https://github.com/SigNoz/engineering-pod/issues/1820
• What is the need of aggregation operator, aggregation attribute and group by clause in the traces tab? #6063
• https://github.com/SigNoz/engineering-pod/issues/1667
• https://github.com/SigNoz/engineering-pod/issues/1390
• [EPIC] Trace Performance Improvements #5713
• Show heatmap of latency and count as axes
• Show if a span is anomalous
• Breakdown by other attributes to figure the outlier attribute
• Show me the attributes which are common to selected spans with >p90 latency and having errors

PRD at https://www.notion.so/signoz/Trace-Explorer-Improvements-103fcc6bcd198042b644f3ab3626deba?pvs=4