[Bug] ANRs Persist in Database Without Expiry

Describe the bug

ANR (Application Not Responding) reports are stored in the database, and while the most recent one is sent to the backend and removed, older ANRs that exist within the 3-hour window may remain in the database indefinitely. This could cause outdated ANRs to persist without proper cleanup, affecting app performance and database management.

How to Reproduce

1. Trigger multiple ANRs within the app.
2. The most recent ANR is sent to the backend and removed from the database.
3. ANRs older than the most recent one remain stored.
4. After 3 hours, observe that older ANRs are still in the database.

Expected behavior

The ANRs should either be cleared from the database after a set time window (3 hours in this case) or there should be a mechanism to regularly purge outdated ANRs to prevent them from persisting unnecessarily.
We can use DatabaseCleanupObserver

Environment

All app versions.

Start by locating DatabaseCleanupObserver and the code that stores and removes ANR reports. Trace how the three-hour window is applied, then verify that older reports are purged rather than left indefinitely, using the reproduction steps to confirm the cleanup behavior.