[DDG stacked - 3] MouseOver UX for DDG graphs

[tiffon]

Which problem is this PR solving?

In DDG graphs, it's not usually possible to discern which nodes share path membership.

Short description of the changes

Add a hover effect that highlights nodes and edges that share path membership with the node being hovered.

Changes in this PR: cde52bb ... 5cd94bd

Before mouse over:

With mouse over:

Before mouse over:

With mouse over:

[codecov]

Codecov Report

Merging #439 into master will decrease coverage by 1.25%.
The diff coverage is 43.51%.

@@            Coverage Diff             @@
##           master     #439      +/-   ##
==========================================
- Coverage    90.3%   89.04%   -1.26%     
==========================================
  Files         180      183       +3     
  Lines        4145     4227      +82     
  Branches     1002     1020      +18     
==========================================
+ Hits         3743     3764      +21     
- Misses        357      417      +60     
- Partials       45       46       +1

Impacted Files	Coverage Δ
packages/jaeger-ui/src/types/index.tsx	0% <ø> (ø)	⬆️
...onents/DeepDependencies/Graph/getNodeRenderers.tsx	7.14% <0%> (ø)
...mponents/DeepDependencies/Graph/DdgNodeContent.tsx	42.42% <0%> (ø)	⬆️
...s/jaeger-ui/src/model/ddg/GraphModel/getEdgeId.tsx	0% <0%> (ø)
...kages/jaeger-ui/src/model/ddg/getStateEntryKey.tsx	100% <100%> (ø)
packages/jaeger-ui/src/reducers/ddg.tsx	100% <100%> (ø)
packages/jaeger-ui/src/actions/ddg.tsx	100% <100%> (ø)
...c/model/ddg/GraphModel/getDerivedViewModifiers.tsx	18.91% <18.91%> (ø)
...components/DeepDependencies/Graph/getSetOnEdge.tsx	25% <25%> (ø)
...aeger-ui/src/components/DeepDependencies/index.tsx	76.31% <28.57%> (-15.36%)	⬇️
... and 8 more

---

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 e9645b2...0bc57bc. Read the comment docs.

[everett980]

I think there are some opportunities for clean up / clarity / naming (the hardest programming challenge) but big-picture looks great.

[everett980]

I believe this is inconsistent with the style guide wrt import order

[saminzadeh]

Can style issues like this be caught with an eslint rule?

[everett980]

i don't believe linters examine the contents of imports as that could be expensive. I'll look into it as the paradigm of separating types from contents isn't rare but a quick look suggests that it's not supported.

[everett980]

LGTM now. Changes ended up being fairly minor (updated some names, styling consistency, and not-yet-linted stylistic patterns).