Convert select component types to interface in TS typegen (#56809)

[huntie]

Summary:

Motivation

Adds (preserves) compatibility of Nativewind and Expo Web type augmentations with the Strict TypeScript API.

• These libraries rely on key React Native component types being defined as interface, not type, since TS module augmentation only supports interface declarations.
• Previously, our opt-in generated TypeScript types (Strict TypeScript API) emitted all props types as type Foo = Readonly<...> ), matching Flow source. However, this API change vs our manual types (which predominantly used interface on props) breaks library compatibility in these cases.
• This is very awkward to otherwise solve in user space — so opt for backwards compatibility in our new types.

Primer

TypeScript module augmentation lets a library extend an existing module's types without modifying the source.

e.g. In Nativewind (source):

declare module 'react-native' {
  interface ScrollViewProps extends ViewProps, ScrollViewPropsIOS, ScrollViewPropsAndroid, Touchable {
    contentContainerClassName?: string;
    indicatorClassName?: string;
  }
  interface FlatListProps<ItemT> extends VirtualizedListProps<ItemT> {
    columnWrapperClassName?: string;
  }
  interface ViewProps {
    className?: string;
  }
}

Expo's react-native-web.d.ts (source) also follows the same pattern across several component props types.

Changes

Add new build-types transform, implementing an opt-in /** build-types emit-as-interface */ annotation, converting eligible type aliases to interface declarations.

• Changing the Flow source files directly isn't viable — Flow doesn't support interface extends Omit<>, and several of these types use Omit<> in their composition. The post-transform operates on the TypeScript output where interface extends Readonly<Omit<...>> is valid.

The following emitted types are updated:

Type	Augmented by	Source
ViewProps	className?	Nativewind, Expo
ScrollViewProps	contentContainerClassName?, indicatorClassName?	Nativewind
ImagePropsBase	className?	Expo
SwitchProps	className?	Expo
TouchableWithoutFeedbackProps	className?	Expo
InputAccessoryViewProps	className?	Expo

FlatListProps is not included in this PR: its bare intersection (no Readonly<> wrapper) has a conflicting fadingEdgeLength property across constituent types that cannot be expressed as a single extends clause without hitting TS2320. This will be addressed in a follow-up.

VirtualizedListWithoutRenderItemProps<T> in react-native/virtualized-lists is separately owned and not changed here.

Changelog:
[General][Changed] - Strict TypeScript API: Select component props types are now interface declarations, enabling module augmentation by libraries like NativeWind and Expo (preserve compatibility)

Differential Revision: D104808984

[meta-codesync]

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

[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

[react-native-bot]

This pull request was successfully merged by @huntie in db89600

^{When will my fix make it into a release? | How to file a pick request?}

[meta-codesync]

This pull request has been merged in db89600.