Improved experience for exception groups

### Problem Statement

[Prior work on exception groups](https://github.com/getsentry/sentry/issues/37716#issuecomment-1409618119)

In heavier concurrency use cases, our issue details UI for [grouped exceptions](https://pypi.org/project/exceptiongroup) can increase friction for users when it comes to extracting meaningful detail from stack traces.

Execution flow paradigms (e.g. [structured concurrency](https://trio.discourse.group/t/structured-concurrency-kickoff/55)) can result in users needing (clicking a lot) to go (n) levels deep to find the meaningful exception within a series of parent child exception groups.

This will be valuable for anyone using trio, anyio or the stdlib asyncio.TaskGroup, or any other form of structured concurrency / analogous constructs in other languages.

### Solution Brainstorm

1. An option to collapse chains of certain exception types (e.g., `NonBaseMultiError` and `ExceptionGroup` when they have only a single child) into one trace

2. There were a better UI option to deal with deeply-nested exceptions than repeated clicking. Some type of auto grouping perhaps.

### Product Area

Issues