[Native] display: contents based button styling (#3634)

## Description

Changes the button implementation of the native `GestureHandlerButton`
component, not to re-export the button component. Instead, it provides a
"sandwich" implementation based on `display: contents`.

The issues we had with the styling of the buttons in the past stemmed
from it extending `ViewGroup` instead of `ReactViewGroup`. This cannot
be changed due to the difference in handling of `onTouchEvent`. We
experimented with wrapping the button with a `View` in the past, but
properly handling layout turned out to be quite a challenge. Hopefully,
with the addition of `display: contents`, this will be easier now.

This PR changes the structure of the button to be:
- `RNGestureHandlerButtonWrapperNativeComponent`
  - `View`
    - `ButtonComponent`

The styles passed from the user are split into two categories:
- visual only
- affecting layout

Those affecting the layout need to be set on the button itself, while
visual changes need to be set on the View wrapping it. Exceptions are:
`zIndex`, `transform`, and `transformOrigin`, which need to be on the
View. `zIndex` because the View is being rendered in the hierarchy at
the level the button would be expected, and transforms to properly
calculate touch coordinate transforms.

### Why not just `ButtonComponent`?

We need a `View` component as its parent to handle all styles that React
Native supports properly.

### Why not just `ButtonComponent` wrapped with `View`?

In order for the view to always match the layout of the button, we need
to set it at the shadow node level. Shadow nodes only have references to
their children, not their parents. To have access to the layout of the
button and the ability to copy it to the view wrapping it, there needs
to be one more node as the parent of that subtree. That node is
responsible for making sure that the size and positioning of the View
match the Button.

The native components for the wrapper serve no purpose, since it's being
rendered with `display: contents`, but RN doesn't know that - there
needs to be something it can link to.

## Test plan

See the `ContentsButton` file

---------

Co-authored-by: Michał Bert <63123542+m-bert@users.noreply.github.com>

Author: j-piasecki

apps/basic-example/ios/Podfile.lock

@@ -2919,7 +2919,7 @@ SPEC CHECKSUMS:
   FBLazyVector: a293a88992c4c33f0aee184acab0b64a08ff9458
   fmt: a40bb5bd0294ea969aaaba240a927bd33d878cdd
   glog: 5683914934d5b6e4240e497e0f4a3b42d1854183
-  hermes-engine: db854ab6e74b584dc130d3ed0be3425726bac226
+  hermes-engine: eec912f8a125ae0d3ad67b2e7b81a227319aa13b
   RCT-Folly: 846fda9475e61ec7bcbf8a3fe81edfcaeb090669
   RCTDeprecation: 2b70c6e3abe00396cefd8913efbf6a2db01a2b36
   RCTRequired: f3540eee8094231581d40c5c6d41b0f170237a81
@@ -2993,7 +2993,7 @@ SPEC CHECKSUMS:
   RNReanimated: 987d0b9af435441cc2ebc2a32ad06cafe8777d4e
   RNWorklets: 12b2d7cdcb48acbdd0b324d1fa810f849089bd7b
   SocketRocket: d4aabe649be1e368d1318fdf28a022d714d65748
-  Yoga: 6ca93c8c13f56baeec55eb608577619b17a4d64e
+  Yoga: 7a9f26c70daf0b08d82ec2f862e9a8872442129e
 
 PODFILE CHECKSUM: ecce038d8e4749ee17b7dea28be0590cdc8b4836
 

apps/basic-example/src/App.tsx

@@ -7,6 +7,7 @@ import Navigator from './Navigator';
 import Text from './Text';
 import NativeDetector from './NativeDetector';
 import RuntimeDecoration from './RuntimeDecoration';
+import ContentsButton from './ContentsButton';
 
 const EXAMPLES = [
   {
@@ -21,6 +22,10 @@ const EXAMPLES = [
     name: 'Native Detector',
     component: NativeDetector,
   },
+  {
+    name: 'Contents Button',
+    component: ContentsButton,
+  },
 ];
 
 const Stack = Navigator.create();