The trace detail page should accurately render the correct number of spans, regardless of duplicate entries. Otherwise, it creates confusion by giving the impression that some spans might be missing.

OSS user reported it here https://signoz-community.slack.com/archives/C01HWQ1R0BC/p1740940431302109

Reported internally too.

A bigger problem is, how to take care of duplication of spans, but there's no easy way to control that at ingestion, it can happen at the SDK level, at the collector on the user side, or at the consumer collector while processing the batch. That issue is captured here #7281