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]()

從連結的 Notion 腦力激盪來源開始；issue 未指定任何 repository 檔案、測試或進入點。比較以元件為基礎的分組、umbrella 分組和具元件感知的主執行緒指紋，然後在實作之前記錄決定採用的模型及其取捨。

由索引模型根據 Issue 內容生成。