feat(trace-eap-waterfall): Rendering orphan errors from new eap endpoint

[Abdkhan14]

The goal of the PR is to support rendering an individual row for orphan errors (type below), in the trace waterfall:

type EAPError = {
  event_id: string;
  event_type: string;
  issue_id: number;
  level: Level;
  project_id: number;
  project_slug: string;
  start_timestamp: number;
  transaction: string;
  description?: string;
};

Bulk of the PR involves using guards to ensure feature parity with other event types already existing in the waterfall.

Added tests.

[codecov]

❌ 2 Tests Failed:

Tests completed	Failed	Passed	Skipped
10068	2	10066	5

View the top 2 failed test(s) by shortest run time

trace view pageload scrolls to trace error node

Stack Traces | 0.543s run time

Error: expect(received).toBe(expected) // Object.is equality

Expected: true
Received: false
    at Object.<anonymous> (.../performance/newTraceDetails/trace.spec.tsx:988:61)

EventTraceView renders a trace

Stack Traces | 1.47s run time

Error: Unable to find an element with the text: MaybeEncodingError: Error sending result. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible.

Ignored nodes: comments, script, style
...
    at waitForWrapper (.../sentry/sentry/node_modules/@.../dom/dist/wait-for.js:163:27)
    at .../sentry/sentry/node_modules/@.../dom/dist/query-helpers.js:86:33
    at Object.<anonymous> (.../interfaces/performance/eventTraceView.spec.tsx:119:46)

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}