[release/9.2] Ensure visible trace spans stay sorted by start time and fix Traces view expand/collapse icons

[JamesNK]

Backport of #8771

Customer Impact

Spans can be displayed out of order, creating a confusing experience when viewing the traces.
Also, collapsing spans isn't working, preventing users from collapsing spans to focus on certain data in the trace view.

Testing

A unit test has been added and a diff is included in the original PR if manual testing is desired as well.

Manual test before:

Manual test after:

Risk

This is a small, isolated, tested change where the root cause is well understood.

Regression?

Yes

[Copilot]

Pull Request Overview

This pull request backports a fix to ensure that visible trace spans are sorted by start time and resolves an issue with the expand/collapse icons in the Traces view.

• Added tests to validate the correct ordering of spans and toggle behavior for span collapse/expand.
• Updated the TraceDetail component to filter out hidden spans and accurately compute the total item count.
• Enhanced the Stress playground applications with new HTTP commands and OpenTelemetry sources to simulate nested trace spans.

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
tests/Aspire.Dashboard.Components.Tests/Pages/TraceDetailsTests.cs	Added tests for span ordering and collapse toggle behavior
src/Aspire.Dashboard/Components/Pages/TraceDetail.razor.cs	Updated GetData filtering logic and added a refresh data call after collapse toggle
playground/Stress/Stress.AppHost/Program.cs	Added a new HTTP command for simulating out-of-order nested spans
playground/Stress/Stress.ApiService/Program.cs	Added OpenTelemetry enhancements and a new endpoint for nested trace spans