feat(frontend): add independent trace vs test data

[jorgeepc]

This PR introduces the initial work to isolate the trace tab data vs the test tab data. The proposed solution was created with the following key points in mind:

• Follow recommended redux architecture to keep state minimal and derive additional data
• Use memoized selectors for optimization only when needed
• One single derived data model that could be used across UI components (not only DAG). Unify current types
• Take advantage of the "built-in" node factory pattern that is part of the DAG lib react-flow

TestRun derived data

The idea of the custom useSpanData hook is to have one single component subscribed to updates in the redux state. This hook is responsible of providing span related data, such as: span details and span specific analyzer errors, test specs and test outputs. The selectors used by this hook are optimized and memoized only if needed. Here we are fixing critical performance issues that were introduced by our previous approach.

classDiagram
    useSpanData <|-- TestRun_selectors
    TestRun_selectors <|-- TestRun_service
    useSpanData: span
    useSpanData: analyzerErrors
    useSpanData: testSpecs
    useSpanData: testOutputs
    class TestRun_selectors{
        Optimized Selectors with Memoization
        selectSpanById()
        selectAnalyzerErrorsBySpanId()
        selectTestSpecsBySpanId()
        selectTestOutputsBySpanId()
    }
    class TestRun_service{      
      Helper methods to transform test run data 
    }

UI components

DAG UI components (react-flow built-in factory)

classDiagram
    TraceSpanNode <|-- BaseSpanNode
    TraceSpanNode: useSpanData
    TraceSpanNode: -span
    TraceSpanNode: -analyzerErrors
    TestSpanNode <|-- BaseSpanNode
    TestSpanNode: useSpanData
    TestSpanNode: -span
    TestSpanNode: -testSpecs
    TestSpanNode: -testOutputs
    class BaseSpanNode{
        Base UI component
    }    

AttributeList UI components

classDiagram  
    class SpanDetail{
        useSpanData
        -span
        -analyzerErrors
        -testSpecs
        -testOutputs
    }

Fixes

• [Analyzer] UX - Errors Isolation #2780

Checklist

• tested locally
• added new dependencies
• updated the docs
• added a test

[xoscar]

Awesome job @jorgeepc 🔥 I left some comments and concerns, let me know what you think