Remove SafeAreaView from public API

[zoontek]

Summary:

Removes the deprecated public SafeAreaView component (deprecated since 0.81). Use react-native-safe-area-context instead.

The native implementation is kept, since RN internals (LogBox, InputAccessoryView, element Inspector) still rely on it via SafeAreaView_INTERNAL_DO_NOT_USE. The few internals that imported the public component now import the internal wrapper.

See #57384

Changelog:

[GENERAL] [REMOVED] - Remove deprecated SafeAreaView component

Test Plan:

• yarn flow-check: 0 errors
• yarn test-typescript: passes
• yarn jest packages/react-native/Libraries/LogBox: passes
• require('react-native').SafeAreaView is undefined

[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: BREAKING

[rubennorte]

Thanks for working on this! We should follow the approach we've been following with other deprecated APIs. We should export a value in DEV that fails, and then remove it in a couple of releases.

[zoontek]

@rubennorte Added ✅ (I followed the InteractionManager example)

[meta-codesync]

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

[alanleedev]

Unfortunately SafeAreaView cannot be removed yet until we migrate all the uses within Meta internal codebase. This is an issue since Meta uses a monorepo and has direct dependency on the codebase without versioning.