Convert additional Props/Style types to interface

[huntie]

Summary

In response to this comment: #57490 (comment)

The DefinitelyTyped react-native-web types augment the react-native module to layer web-only props and style values onto React Native's types. Module augmentation only works against interface declarations, so these hit error TS2300: Duplicate identifier.

This was solved in #56809 — this diff extends interface emission to additional types as below.

Changes

Annotate the remaining types that @types/react-native-web augments with @build-types emit-as-interface:

• AccessibilityProps
• ImageProps
• PressableStateCallbackType
• ViewStyle, TextStyle, ImageStyle

Source for matched @types/react-native-web conflicts

Type	Declared in	Augmented by @types/react-native-web
AccessibilityProps	Libraries/Components/View/ViewAccessibility.js:342	index.d.ts#L1272
ImageProps	Libraries/Image/ImageProps.js:336	index.d.ts#L1422
PressableStateCallbackType	Libraries/Components/Pressable/Pressable.js:36	index.d.ts#L1444
ViewStyle	Libraries/StyleSheet/StyleSheet.js.flow:141	index.d.ts#L1458
TextStyle	Libraries/StyleSheet/StyleSheet.js.flow:159	index.d.ts#L1486
ImageStyle	Libraries/StyleSheet/StyleSheet.js.flow:177	index.d.ts#L1514

Not fixed

The remaining DT failures (parsed from https://github.com/DefinitelyTyped/DefinitelyTyped/actions/runs/32138113480) aren't interface issues:

• InteractionManager has no export in the Strict API at all.
• VirtualizedListProps is genuinely non-generic in the Flow source (packages/virtualized-lists/Lists/VirtualizedListProps.js:287), and getItem / getItemCount are required there. DT's VirtualizedListProps<ItemT> with those omitted is an assumption carried over from the old hand-written types.
• The ViewStyle / TextStyle / ImageStyle "incorrectly extends WebStyle" errors will persist. RN's DimensionValue includes null, and DT redefines bottom?: CSSProperties["bottom"] | DimensionValue on an interface extending WebStyle, whose bottom does not accept null. DT needs Exclude<DimensionValue, null> there. Expect 3 of the 16 reported errors to remain once the duplicate-identifier ones clear.

cc @jakebailey

Changelog:
[General][Fixed] - JS API: Additional Props/Style types are now defined as interface, fixing compatibility with certain DefinitelyTyped packages

Test Plan

• node ./scripts/js-api/build-types — snapshot regenerated; --validate passes
• yarn test-generated-typescript, yarn test-typescript — pass
• yarn jest scripts/js-api — 141 tests pass
• Scratch project replaying react-native-web's augmentations against types_generated: all six now merge cleanly. As a control, augmenting ImagePropsAndroid (still a type alias) in the same harness reproduces error TS2300: Duplicate identifier, confirming the harness detects the failure mode.

[github-actions]

Warning

JavaScript API change detected

This PR commits an update to ReactNativeApi.d.ts, indicating a change to React Native's public JavaScript API.

• Please include a clear changelog message.
• This change will be subject to additional review.

This change was flagged as: POTENTIALLY_BREAKING

[jakebailey]

Do you have any timeline for when you think this (or a similar PR) might be merged and released? The types break is blocking PRs to any react types on DT.

[huntie]

@jakebailey As soon as this gets merged, I'll raise a pick request into the 0.87 branch, then it'll go out in the next patch release (typically Mondays).

cc @zeyap @cortinico

[cortinico]

@huntie can you fix the conflicts with main?

[huntie]

@cortinico Done

[meta-codesync]

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

[meta-codesync]

@cortinico merged this pull request in 593ae02.

[jakebailey]

@jakebailey As soon as this gets merged, I'll raise a pick request into the 0.87 branch, then it'll go out in the next patch release (typically Mondays).

cc @zeyap @cortinico

@huntie I'm not sure that this happened; were you still working on the other breaks? I see #58168 now, but still hoping to get DT unbroken...

[huntie]

@jakebailey Yes, opened here: reactwg/react-native-releases#1399. Waiting on the Release Crew to deploy this in the next patch.