SDK sets the wrong transaction to ANR events detected during navigation.

### Integration

sentry-android

### Build System

Gradle

### AGP Version

NA

### Proguard

Enabled

### Other Error Monitoring Solution

No

### Version

8.32.0

### Steps to Reproduce

This is a hard-to-reproduce issue as it seems to happen only when an ANR is detected while the user is navigating between views in the Android app.

The order of events is:
1. User is in ScreenA
2. User Navigates to Screen B (This creates a new transaction in the SDK scope, replacing the transaction from ScreenA)
3. During the navigation, the app is killed/ANR event is detected
4. The SDK sends the ANR event associated with the transaction from ScreenB

### Expected Result

The ANR event's transaction matches the stack trace and other information in the event.

### Actual Result

The ANR event in Sentry has the stack trace pointing to ScreenA, with all other information pointing to this view. However, the event's transaction (and by extension the event's culprit) points to ScreenB.

This causes user confusion as the culprit showing next to the issue's title now points to a view unrelated to the stack trace where the ANR happened.

[Code where the culprit is set in Sentry. ](https://github.com/getsentry/sentry/blob/master/src/sentry/culprit.py)

Start with the linked src/sentry/culprit.py to understand how the transaction affects the culprit, then trace sentry-android navigation transaction handling and ANR event capture. Reproduce the ScreenA-to-ScreenB navigation sequence if possible; done means the ANR event's transaction and culprit match the screen represented by its stack trace.

Written by the indexing model from the issue text.