feat: GroupTreePlot --- Refactor to typescript + better D3 and React intergation + some small features

[Anders2303]

Resolves #1829

• refactor: Fully rewrites the old D3-only GroupTreePlot component to more seemlessly use both D3 and React to build the graph
  • In essence; D3 is now purely used to calculate hierarchies and node positions, whilst React handles the rendering of said nodes
  • D3 is also used to animate transitions between graph states (assisted by React to trigger the animation changes)
• dependency: Installed the react-transition-group package to facilitate leave-enter transitions for graph elements
• refactor: groupTreeAssembler has been replaced; it has been split it into by react components (to handle svg rendering), and the new DataAssembler class, to handle the data itself. Rewritten in proper Typescript
• fix: The rendered tree is now more centered in the SVG
• fix: The tree will now fill the entire width of the SVG
• feature/fix: Child nodes can now be minimized and expanded, as intended
• feature: Added initialVisibleDepth; renders the tree with all nodes from the given depth collapsed
• feature: The plot is now fully resizable.
  • An example of resizing is show in the "Resizable" Story (/?path=/story/grouptreeplot-demo--resizable)

Known issue (slight animation regression)

Because each component initializes their own enter/leave animations in their enter/leave-callbakcs, the D3 animations get slightly de-synchronized, so new/old tree edges get slightly "detached" from the tree when it grows shrinks (only during the animation). The d3 only version did not have this issue (as it set up all animations in one single update), so it's a regression.

However, this is only noticable in slower animations, and with a 200ms transition duration, it's more or less impossible to notice, so I'm leaving it unresolved for now

[Anders2303]

Convert this comment to an issue when this is merged
As mentioned in the PR, the tree edge animation experiences some "lag" when the tree experiences rapid updates. I believe this issue is mainly caused by the animations starting within the enter/leave callbacks. I think we should instead use the callbacks to build the "target" state for the edge (likewise with changes to width and path from external updates), then initiate d3-animation call in a singular effect-hook after the component is done rendering