Order global tracks by activity and select the most active non-parent process by default

[canova]

Previously we were keeping the original order in the profile data structure when we were initializing the global track order, and selecting the first tab visible process by default. But this was mostly incorrect for the cases where we have more than one visible tab process, because usually busier thread arrives later during the profile collection.

This should help our users to see the most active process very quickly instead of having to scroll down every time.

Deploy preview / main branch

[codecov[bot]]

Codecov Report

Attention: Patch coverage is 98.21429% with 1 line in your changes missing coverage. Please review.

Project coverage is 86.13%. Comparing base (5c7515a) to head (fc1a8d3). Report is 9 commits behind head on main.

Files with missing lines	Patch %	Lines
src/profile-logic/tracks.js	98.14%	1 Missing :warning:

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5491      +/-   ##
==========================================
+ Coverage   86.11%   86.13%   +0.01%     
==========================================
  Files         308      308              
  Lines       29652    29673      +21     
  Branches     8001     8017      +16     
==========================================
+ Hits        25534    25558      +24     
+ Misses       3528     3525       -3     
  Partials      590      590              

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

:rocket: New features to boost your workflow:

• :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• :package: JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[canova]

@julienw It should be ready for review now. Let me know what you think!