Fix RefreshControl jest mock to forward props

[psjostrom]

Summary:

The RefreshControl jest mock renders <RCTRefreshControl /> without forwarding any props. This is inconsistent with the ScrollView mock, which spreads {...this.props} to its native component.

This has two consequences:

1. The rendered RefreshControl is invisible to RNTL host queries. Props like testID and accessibilityLabel are not forwarded to the native component, so getByTestId, getByLabelText, etc. cannot find it. The only way to locate it is UNSAFE_getByType.

2. Props transformed internally by wrapper components are inaccessible. When a component wraps RefreshControl and transforms props before passing them down (e.g. wrapping onRefresh with throttle/debounce), the rendered native component should receive the transformed props. But since the mock discards all props, there is no way to access the transformed values without UNSAFE_getByType. The RNTL-recommended pattern of list.props.refreshControl.props.onRefresh() only gives the original untransformed props from the React element descriptor.

The fix spreads this.props onto RCTRefreshControl in both mock files, matching how the ScrollView mock already works. The HostComponent generic is also updated from {} to RefreshControlProps for proper typing.

Changelog:

[GENERAL] [FIXED] - Forward props in RefreshControl jest mock to make testID, onRefresh, and other props visible to testing library queries

Test Plan:

Before this change, rendering a RefreshControl with testID="my-control" produces:

<RCTRefreshControl />

After this change:

<RCTRefreshControl testID="my-control" onRefresh={[Function]} refreshing={false} ... />

This enables standard RNTL queries:

screen.getByTestId('my-control').props.onRefresh();

Instead of requiring:

screen.UNSAFE_getByType(RefreshControl).props.onRefresh();

[meta-cla]

Hi @psjostrom!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!