Pull model: pull each surface's pending transaction at the start of the mount phase (#59029)

[bartlomiejbloniarz]

Summary:
With enableMountingCoordinatorPullModelAndroid, each commit notification queues a PullTransactionMountItem in MountItemDispatcher. MountingCoordinator::pullTransaction mounts the latest revision, so a surface's first queued item mounts every pending commit and its later items pull nothing. The item's queue position only reflects when the notification arrived.

The queued item breaks root view attach. While the root view is detached, the item waits in the surface's attach queue, ahead of the preallocations for the revisions it pulls. #58152 handles this by re-queueing the pulled batch on the dispatcher. That puts the batch behind a later pull of the same surface, so the newer revision mounts first.

This PR replaces the queued item with the set of surfaces that have a transaction available. A dispatch runs view commands, then pre-mount items, then one FabricUIManagerBinding.pullAndExecuteTransaction per pending surface whose root view is attached, then the queued mount items. Pulls share the mount items' "mount" trace, their handling of ignorable mounting exceptions, and reportMount. A surface waiting for its root view stays pending. Its attach already runs through MountingManager.MountItemExecutor, which now also schedules a frame, and that frame pulls the surface after its preallocations. This removes the #58152 re-queue and PullTransactionMountItem. With disableIdleMountItemFrameCallbackRearmAndroid, an attached pending surface keeps the frame callback armed, like a queued item.

When a dispatch has both a pending surface and queued mount items, it now pulls the surface first. On main, an item queued before the surface's first pull notification ran before the pull. Push behaves like main here: its batch is queued at the end of the JS task, behind the items queued during it. An item that targets a view the commit creates, such as an accessibility event or a SynchronousMountItem, now finds it. An item that targets a view the commit deletes now misses it, although that view is gone after this frame either way. It logs a soft exception and is dropped, or for a view command, retries once first. With the default flags, view commands still run before the pulls, as on main.

Changelog:

[ANDROID] [FIXED] - Pull model: fix batches applied out of order when a surface's root view attaches

Test Plan:
FabricUIManagerPullModelTest models each surface's MountingCoordinator: a pull mounts every revision committed since the previous pull, as one batch.

./gradlew :packages:react-native:ReactAndroid:testDebugUnitTest \
  --tests 'com.facebook.react.fabric.*'

Test	Before	After
pullDeferredByRootAttach_isAppliedBeforeLaterPulls	fails: revisions mount as 3, 1, 2	passes
onTransactionAvailable_pullsEachPendingSurfaceOnce	fails: pulls [1, 2, 1, 3]	passes
mountItemQueuedBeforeCommit_runsAfterThePull	fails: the item runs before the batch	passes
pendingPullOfStoppedSurface_runsOnceAndIsDropped	fails: the stop clears the queued pull, nothing is pulled	passes
viewCommandsInMountItemOrder_runAfterThePull	fails: the command dispatched before the commit runs before the batch	passes

• The new tests for pre-mount items, reportMount and the frame callback with disableIdleMountItemFrameCallbackRearmAndroid pass before and after. One of them, a commit notified from the commit thread while a frame pulls another surface, fails if hasPendingItems ignores pending surfaces.
• onTransactionAvailable_enqueuesOnePullPerNotification is now onTransactionAvailable_pullsEachPendingSurfaceOnce. synchronousBatch_waitingForRootAttach_isDeferred is removed, because a synchronous batch can no longer run while its root view is detached.
• All ReactAndroid JVM tests pass.
• A few one-off checks, not committed, passed on main and with this PR: commits on two surfaces, an item queued after a commit, and a dispatch without a commit. A push-model check also passed, with the pull flag on: batches queued around a root view attach apply in commit order.
• RNTester debug on an Android emulator with enableMountingCoordinatorPullModelAndroid, enableAccumulatedUpdatesInRawPropsAndroid and enablePreallocatedPropsDiffOnInsertAndroid: FlatList, Image, Animated and Accessibility examples render and update, including after leaving and reopening the app. There were no crashes or mounting exceptions.

Differential Revision: D124966304

Pulled By: bartlomiejbloniarz

[meta-codesync]

@bartlomiejbloniarz has imported this pull request. If you are a Meta employee, you can view this in D124966304.

[meta-codesync]

@bartlomiejbloniarz has exported this pull request. If you are a Meta employee, you can view the originating Diff in D124966304.