tools: restore descending test timing order with --time

[Uziniii]

The --time option displays only the first 20 entries after sorting test durations. The current ascending sort therefore reports the fastest tests.

Before 1fc4255221, CompareTime() sorted durations in descending order.
That commit replaced the comparator with an ascending key-based sort while modernizing the Python code.

Sort durations in descending order to restore the historical behavior and report the tests that contribute most to the suite's execution time.

This also matches the output documented in: #27007

The change was verified with:

$ python3 tools/test.py --mode=release --time -j1 -p dots \
    parallel/test-inspector-not-blocked-on-idle \
    parallel/test-http-methods
   1 (00:01.391) release test-inspector-not-blocked-on-idle
   2 (00:00.106) release test-http-methods

AI assistance was used to investigate the Git history and write this description as im not a native english. I reviewed and verified the change.

[lpinca]

It seems that the original implementation was also sorting in ascending order

node/tools/test.py

Line 1756 in a16a0fe

timed_tests.sort(lambda a, b: a.CompareTime(b))

#65603 (comment)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.05%. Comparing base (65f518c) to head (9fcf6df).
⚠️ Report is 122 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #65603      +/-   ##
==========================================
- Coverage   90.12%   90.05%   -0.07%     
==========================================
  Files         751      751              
  Lines      252638   254919    +2281     
  Branches    47551    48130     +579     
==========================================
+ Hits       227689   229579    +1890     
- Misses      16238    16520     +282     
- Partials     8711     8820     +109     

see 93 files with indirect coverage changes

🚀 New features to boost your workflow:

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