Group ANRs by component (UI, BroadcastReceiver, Service, etc.)

Revisit the ANR grouping strategy by evaluating two approaches: grouping ANRs by Android component type (UI, BroadcastReceiver, Service) for faster filtering, versus collapsing all ANRs into a single umbrella issue for visibility without polluting the issue stream. Both trade-offs should be considered before committing to one model.

We could also add an additional fingerprint, so they are still grouped by the main thread stacktrace, but within the component groups.

**Votes in brainstorming session:** 3

**Notion source:** [https://www.notion.so/3348b10e4b5d80d999d5fb7b4cabfe60]()

Comece pela fonte de brainstorming vinculada no Notion; a issue não menciona arquivos do repositório, testes ou pontos de entrada. Compare o agrupamento baseado em componentes, o agrupamento guarda-chuva e as impressões digitais da main thread cientes de componentes e documente um modelo escolhido e seus trade-offs antes da implementação.

Escrita pelo modelo de indexação a partir do texto da issue.