Improve performance when expanding/collapsing span details

[DamianMaslanka5]

Improve performance when expanding/collapsing span details (tags/process)

Related to #645

Memoize "calculation" of criticalPathSections per span, when span is not collapsed

Prepare data

Run go run cmd/tracegen/main.go -service abcd -traces 1 -spans 300 from the jaeger repo

Perf difference

Total render time from the profiler available in react devtools, after collapsing Tags section

With these changes

14ms

Changes from master

548ms

firefox_Ddmz0w1Z7u.mp4

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.69%. Comparing base (d5a9de9) to head (2d53046).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2716   +/-   ##
=======================================
  Coverage   96.68%   96.69%           
=======================================
  Files         256      256           
  Lines        7884     7889    +5     
  Branches     2061     2060    -1     
=======================================
+ Hits         7623     7628    +5     
+ Misses        261      260    -1     
- Partials        0        1    +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 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.

[DamianMaslanka5]

1. I ran npm run prettier to fix CI 1a65b43
2. I replaced import { groupBy } from 'lodash'; with import _groupBy from 'lodash/groupBy'; to match style of other imports 2d53046

Is there anything else that I can do to make reviewing these changes easier?

[DamianMaslanka5]

Thanks @yurishkuro!

[yurishkuro]

Thanks for contributing