Experiment: Issues tab to show Backend & Frontend errors in a replay session

[billyvg]

Problem: We don't have backend errors associated with replays.

Idea: Can we hack around that issue by making N+1 queries on the front-end?

The task is to query for all errors that've happened within a replay

Currently we can query for all errors, and find that have event.replayId set. But in practice these are only front-end error.

We could find errors if we query for the list of traces within a replay first, but this could be slow.
This wouldn't work if the org doesn't have tracing enabled.

[ryan953]

cc @jas-kas

[ryan953]

We're going to have to do some work to put the table filters (console, dom, network, etc) into the url, so that we can deep link into the details page and have only errors shown in the console tab.
I think that's the task in this ticket right now.

[ryan953]

This is an epic now, spec'd out: #45529

closing because this ticket is a duplicate of that.