Memoize getTraceName to improve render time by 3x

[everett980]

Which problem is this PR solving?

• Rendering large traces on either the trace view or as a search results item took over 51s for a trace with 10k spans.
• Relates to Support loading traces with large number of spans. #562 but does not fully finish it.

Short description of the changes

• Memoizing getTraceName() by traceID cuts the calls to getTraceName() in third, improving performance for a trace with 10k spans from ~51s to ~17s.

[codecov]

Codecov Report

Merging #572 into master will increase coverage by 0.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #572      +/-   ##
==========================================
+ Coverage   90.05%   90.09%   +0.04%     
==========================================
  Files         214      214              
  Lines        5210     5211       +1     
  Branches     1327     1327              
==========================================
+ Hits         4692     4695       +3     
+ Misses        475      473       -2     
  Partials       43       43              

Impacted Files	Coverage Δ
...ents/TracePage/TracePageHeader/TracePageHeader.tsx	96.42% <ø> (ø)
packages/jaeger-ui/src/model/trace-viewer.tsx	100.00% <100.00%> (ø)
...kages/jaeger-ui/src/model/transform-trace-data.tsx	89.41% <100.00%> (ø)
...eViewer/TimelineHeaderRow/TimelineViewingLayer.tsx	91.52% <0.00%> (+3.38%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7b5aecd...d36c0d0. Read the comment docs.