Revert "Export new createNativeWrapper (#3971)" (#4001)

This reverts commit bdf353d.

## Description

We decided that it will be better not to export new
`createNativeWrapper` as it might be confusing when to use it.

## Test plan

Try to import `createNativeWrapper`
Read docs 🤓

Author: m-bert

apps/common-app/src/legacy/basic/pagerAndDrawer/index.android.tsx

@@ -2,11 +2,11 @@ import ViewPagerAndroid from '@react-native-community/viewpager';
 import React, { Component } from 'react';
 import { StyleSheet, Text, View } from 'react-native';
 import {
-  createNativeWrapper,
+  legacy_createNativeWrapper,
   LegacyDrawerLayoutAndroid,
 } from 'react-native-gesture-handler';
 
-const WrappedViewPagerAndroid = createNativeWrapper(ViewPagerAndroid, {
+const WrappedViewPagerAndroid = legacy_createNativeWrapper(ViewPagerAndroid, {
   disallowInterruption: true,
 });
 

packages/docs-gesture-handler/docs/components/create-native-wrapper.mdx

@@ -3,10 +3,11 @@ id: upgrading-to-3
 title: Upgrading to the new API introduced in Gesture Handler 3
 ---
 
-import CodeComparison from '@site/src/components/CodeComparison';
-
 ## Migrating gestures
 
+
+import CodeComparison from '@site/src/components/CodeComparison';
+
 The most important change brought by the Gesture Handler 3 is the new hook API. Migration is pretty straightforward. Instead of calling builder methods, everything is passed as a configuration object.
 
 <CodeComparison
@@ -282,11 +283,7 @@ Other components have also been internally rewritten using the new hook API but
 
 ### createNativeWrapper
 
-`createNativeWrapper` has been rewritten using the new hook API and exported under the original name. The old implementation is still available as `legacy_createNativeWrapper`. It also accepts new optional parameter - `detectorType`, which allows you to specify the type of the [gesture detector](/docs/fundamentals/gesture-detectors) that will be used internally. By default it uses `GestureDetector`.
-
-While new `createNativeWrapper` should work out of the box, keep in mind that it wraps your component with `GestureDetector`, which in Gesture Handler 3 is a host component. This affects view hierarchy, so depending on your use case, you might want to use [`VirtualGestureDetector`](/docs/fundamentals/gesture-detectors#virtualgesturedetector) instead. To do that, simply pass the desired detector type as the second parameter of `createNativeWrapper`.
-
-More on `createNativeWrapper` can be in the [dedicated section](/docs/components/create-native-wrapper) of the documentation.
+`createNativeWrapper` is deprecated and it is now exported as `legacy_createNativeWrapper`.
 
 ## Replaced types
 

packages/docs-gesture-handler/docs/guides/upgrading-to-3.mdx

@@ -20,6 +20,9 @@ const NATIVE_WRAPPER_PROPS_FILTER = [
   'onGestureHandlerStateChange',
 ] as const;
 
+/**
+ * @deprecated `createNativeWrapper` is deprecated and will be removed in favor of using `GestureDetector` with `Native` gesture directly.
+ */
 export default function createNativeWrapper<P>(
   Component: React.ComponentType<P>,
   config: Readonly<NativeViewGestureHandlerProps> = {}

packages/react-native-gesture-handler/src/handlers/createNativeWrapper.tsx

@@ -83,5 +83,3 @@ export {
 export type { ComposedGesture } from './types';
 
 export { GestureStateManager } from './gestureStateManager';
-
-export { default as createNativeWrapper } from './createNativeWrapper';

packages/react-native-gesture-handler/src/v3/index.ts

@@ -171,11 +171,7 @@ The implementation of buttons has been updated, resolving most button-related is
 
 Other components have also been internally rewritten using the new hook API but are exported under their original names, so no changes are necessary on your part. However, if you need to use the previous implementation for any reason, the legacy components are also available and are prefixed with `Legacy`, e.g., `ScrollView` is now available as `LegacyScrollView`.
 
-`createNativeWrapper` has been rewritten using the new hook API and exported under the original name. The old implementation is still available as `legacy_createNativeWrapper`. It also accepts new optional parameter - `detectorType`, which allows you to specify the type of the gesture detector that will be used internally. By default it uses `GestureDetector`.
-
-While new `createNativeWrapper` should work out of the box, keep in mind that it wraps your component with `GestureDetector`, which in Gesture Handler 3 is a host component. This affects view hierarchy, so depending on use case, you might want to use `VirtualGestureDetector` instead.
-
-Before changing, ask user about their intention - if they prefer to keep legacy version, change it to `legacy_createNativeWrapper`. If not, keep `createNativeWrapper`, then notify user that in case of problems with view hierarchy they should wrap the relevant subtree with `InterceptingGestureDetector` and pass `GestureDetectorType.Virtual` as the `detectorType` argument in `createNativeWrapper`.
+Rename all instances of createNativeWrapper to legacy_createNativeWrapper. This includes both the import statements and the function calls.
 
 ### Replaced types