Improve trace application order on traces page

[JamesNK]

Description

The traces page shows a summary of info about it's spans apps . Spans are grouped by app, and then the apps are ordered by its earliest span.

The problem with this is span start dates can be out of order. For example, the start time reported by a .NET app and a browser app could be slightly off, causing a child browser app span to be earlier than its parent server span.

This PR changes the ordering logic so a child can't be ordered before its parent. There are performance improvements that could be made to here, but the old logic wasn't optimized either. Only runs for traces than are rendered to the screen which is limited by virtualization.

Low priority. Post 9.0

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Link to aspire-docs issue:
  • No

Microsoft Reviewers: Open in CodeFlow

[JamesNK]

Many changes. Please take another look.

[JamesNK]

@drewnoakes @adamint