Sort by slowest component in command trace list

[ghabriel25]

Hi, @ganyicz

I think it would make more sense to show the slowest component first in php artisan blaze:trace:list.

[github-actions]

Benchmark Result: Default

Attempt	Blade	Blaze	Improvement
#1 *	339.99ms	15.90ms	95.3%
#2	344.25ms	16.22ms	95.3%
#3	344.11ms	15.78ms	95.4%
#4	347.87ms	15.81ms	95.5%
#5	344.97ms	15.79ms	95.4%
#6	341.33ms	15.80ms	95.4%
#7 *	350.06ms	15.99ms	95.4%
#8	346.29ms	15.98ms	95.4%
#9	344.18ms	15.86ms	95.4%
#10	344.77ms	15.99ms	95.4%
Snapshot	345.32ms	15.81ms	95.4%
Result	344.51ms (~)	15.84ms (~)	95.4% (~)

_{Median of 10 attempts (* = outlier, excluded from result), 5000 iterations x 10 rounds, 45.4s total}

_{To run a specific benchmark, comment /benchmark <name> where name is one of: attributes, aware, class, default, forwarding, merge, named-slots, no-attributes, slot}

[ganyicz]

Thanks!