Fix RefreshControl initial prop replay

[adamivancza]

Summary:

Fixes #56343.

Fixes an iOS Fabric RefreshControl regression where tintColor, title, and titleColor could be skipped during initial prop replay.

RCTPullToRefreshViewComponentView was comparing incoming props against its stored _props instead of the oldProps passed into updateProps. In replay/deferred update paths, _props can already match the incoming props even though the native UIRefreshControl has not received those values, so the native setters were skipped.

This updates the comparison to use oldProps when available, with a fallback to _props for null initial-mount calls.

Changelog:

[IOS] [FIXED] - Fix Fabric RefreshControl initial tintColor and title props not being applied on iOS

Test Plan:

Added RCTPullToRefreshViewComponentViewTests/testUpdatePropsUsesOldPropsWhenReapplyingStoredProps.

Verified the focused unit test passes:

xcodebuild test \
  -workspace packages/rn-tester/RNTesterPods.xcworkspace \
  -scheme RNTesterUnitTests \
  -sdk iphonesimulator \
  -destination "platform=iOS Simulator,name=iPhone 17 Pro,OS=26.5" \
  -derivedDataPath /tmp/RNTesterUnitTestsBuild-RefreshControl \
  -resultBundlePath /tmp/RNTesterUnitTests-RefreshControl.xcresult \
  -only-testing:RNTesterUnitTests/RCTPullToRefreshViewComponentViewTests

[javache]

Comparing with _props is the right behaviour (I know, the API is pretty confusing), as that's the last props the view was configured with, and the view may have been recycled since.

If native properties are not correctly updating, that's a view recycling bug.

[adamivancza]

Comparing with _props is the right behaviour (I know, the API is pretty confusing), as that's the last props the view was configured with, and the view may have been recycled since.

If native properties are not correctly updating, that's a view recycling bug.

oh indeed, I totally missed that. thx for the clarification!