fix(hooks): resync manager after a discarded concurrent render

[NerdyMihir]

Description

Fixes #2527

useRecyclerViewManager calls updateProps(props) and processDataUpdate() during render inside useMemo blocks keyed on [props] / [data]. When React discards a render (Suspense, transitions, useDeferredValue), the manager has already taken the discarded props, but the memo cache from that render is dropped. The next committed render has the same deps as the last commit, so both memos skip and the manager stays on the discarded data. With a longer discarded array, the list renders indices past the committed data: index out of bounds, not enough layouts on 2.3.3, renderItem with item === undefined on 2.0.x.

The fix keeps the last props/data the manager actually received in a useState object and re-syncs whenever the current render's values differ from it. Renders that commit normally behave as before: one updateProps per new props, one processDataUpdate per new data, including the first render.

src/__tests__/useRecyclerViewManager.test.tsx reproduces it on a concurrent react-test-renderer root: a deferred 2→6 row update suspends and is discarded, then an extraData change re-renders. It throws on main and passes with the fix.

Reviewers’ hat-rack 🎩

• yarn test --forceExit, yarn type-check, yarn lint are green locally
• Run the new test with the hook change reverted: it fails with index out of bounds, not enough layouts
• Check whether a list with frequently changing props (no data change) still calls processDataUpdate only when data changes

Screenshots or videos (if needed)

N/A (no visual change)

[NerdyMihir]

Closing; leaving the fix approach described in #2527 for maintainers to take as they prefer.