App Hang / ANR Rate - Need to have more granular Rates for non fatals & fatals or combinations of that

### Problem Statement

Ideally I would like to have insights into all user perceived App Hangs / ANRs.
Currently, the App Hang / ANR rate is only focused on Fatal app hangs, but I think non-fatal hangs could also be user-perceived.

We don't have any Rates about those.

### Solution Brainstorm

Internally we care both about an app hang that recovers or when it doesn't recover, since both of them cause a degraded user experience, and our hypothesis is that both of them end up affecting orders.
having both of them together would be useful for us, since that's the value we actually want to look at.
The follow up would be to have both rates separate: Rate for Non fatals, Rate for Fatals and Rate for combined.

No files, tests, or entry points are named. Start by tracing the existing fatal App Hang/ANR rate, then determine how non-fatal, fatal, and combined rates should be defined and where each should be exposed; done means all three rates are available and their behavior is covered by appropriate tests.

Written by the indexing model from the issue text.