Heat map generation

### Problem Statement

There was [a previous feature request for this](https://github.com/getsentry/sentry/issues/70642), but it was closed because it was deemed that the use-cases were for roles other than developers.

I'd like to reopen that issue, but since there's no option for that, I'm creating a new one.

As a developer, I would find a lot of value out of a heatmap, especially if the heatmap can be rendered with filtering on criteria. It helps get a sense of which interactions can result in crashes at a glance. Without the heatmap, there's a lot of log-diving, code grokking, and critical thinking required at times to identify which behaviors could lead to problems. But with a heatmap filtered to just users on a screen who saw an error, it becomes way easier to see which combination of two button presses caused an error, for example.

Also, the overhead of capturing replays makes it impossible to justify running multiple replay capture solutions. We end up having to choose between Sentry replays or something else.

### Solution Brainstorm

Allow for heatmap visualization alongside dynamic filters for heatmap rendering.

### Product Area

Replays

Start by reviewing the prior request in issue #70642 and the Replays product area named here. The issue names no files, tests, or entry points, so the implementation surface is not yet defined. Done would mean providing heatmap visualization alongside dynamic filters for rendering.

Written by the indexing model from the issue text.