fix(trace-waterfall): Add cycle protections

[nsdeschenes]

This PR makes some changes to the trace tree to add in protection for potential cycles potentially leading infinite loops.

Ticket: EXP-707

Why cycles might happen

Cycles in trace data can occur from:

• Corrupted span data where parent_span_id references create circular dependencies (e.g., span A → B → C → A)
• Duplicate event IDs causing multiple spans to be treated as the same node
• Data ingestion edge cases that incorrectly link spans

What the UI does when cycles are detected

Location	Behavior
Tree construction (traceTree.tsx)	Skips duplicate event_id nodes, logs to Sentry
Span tree (transactionNode.tsx)	Detects ancestor cycles, attaches cyclic spans to transaction root
Traversal methods (baseNode.tsx)	Uses visited Set to skip already-seen nodes
Autogroup segments (parentAutogroupNode.tsx)	Breaks out of loop, renders partial segments

In all cases, the UI renders safely with the non-cyclic portion of the tree rather than crashing or hanging.

[nsdeschenes]

@sentry review
@cursor review

[nsdeschenes]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

[linear]

EXP-707 Browser freezes when opening trace on 25.12.1

[gggritso]

Cool, nice work! The PR could use a more detailed description though. Covering why cycles might happen, and what the UI does in case of cycles would be helpful. Actually adding some of that context to the code would be helpful, too.