[android] when used as material-top-tab with react-navigation, navigation.navigate may not complete screen transition

## Environment

| package | version |
| -------------------------------------- | ------- |
| @react-navigation/native | 7.0.1
| @react-navigation/drawer | 7.0.1
| @react-navigation/material-top-tabs | 7.0.1
| react-native-pager-view |6.5.0
| react-native |0.76.1
| expo |20.0.2
| node | 20
| npm or yarn | 4

## Description

hi! crossposted from https://github.com/react-navigation/react-navigation/issues/12251
I use a custom drawer content to put buttons that navigate to specific screens as material top tabs, which are nested as a drawer screen. since the new arch migration, I observed the sliding transition of the tab screens are 1. too fast; 2. it occasionally does not do a full transition in dev, and almost never in release.
this behavior is not observed in the old arch.
Many thanks for anyone having a look at this!

see the attached video; error occurs toward the very end
https://github.com/user-attachments/assets/42b7e0b4-d784-4ae4-9595-99926aa0126b

## Reproducible Demo

My reproducer is adapted from my app, but I trimmed all of my code and left only Bug.tsx as the actual reproducer.
https://github.com/lovegaoshi/azusa-player-mobile/tree/bug

Commencez par exécuter le reproducer lié, en vous concentrant sur Bug.tsx et la configuration de material-top-tab qui appelle navigation.navigate via le drawer. Comparez la transition dans les architectures nouvelle et ancienne, en builds de développement et de release ; le travail est terminé lorsque la transition de l’onglet se termine à la vitesse attendue sans s’interrompre en cours de route.

Rédigé par le modèle d'indexation à partir du texte de l'issue.