Enhance Trace View navigation, usability, and layout

[alexbikfalvi]

User problem

User feels that the trace view area is very compressed, the information feels haphazard, and it is hard to navigate a large trace and hard to parse. They have the impression that too much information is pushed in their face. This results in a not useful Trace View because there is too much noise. Some data is redundant, it would be nice to turn off or collapse. They want to have a trace view that is much snappier, intuitive, and easy to work with, with fewer steps. They note that most of the work (and demoing) is done at the bottom of the trace view and they thinks that there are many steps to get to see the right information.

User feels that the space (empty box below service&operation) is wasted when expanding a span in the Trace view
User feels that the discrepancy of the font size seems weird and visually is creating confusion (why is the content larger than the heading?)

Goal

We make the trace view more navigable, visually clear, and efficient for troubleshooting large traces. This includes improving the layout to reduce wasted space, enabling more direct filtering and categorization (e.g., database spans), and providing clearer cues (e.g., error highlights, endpoint names, and a more prominent or alternative visualization like a flame graph). By removing clutter, refining font sizes, and offering full-screen or expandable views we can help users locate issues quickly, maintain a sense of place in large traces, and easily focus on the most relevant spans.