[Slider] Fix Android hitSlop by replacing touchArea overlay with responder system

[adids1221]

Description

Fixes an Android bug where touches near the Slider thumb fail to start a drag.

Slider – The touchArea overlay (absoluteFillObject) intercepted touches in the thumb's hitSlop zone before they reached the PanResponder.
Replaced it with the container's Gesture Responder System (onStartShouldSetResponder + onResponderRelease) — the thumb (deepest child) wins for direct touches, the container handles track taps.
hitSlop now works consistently on both platforms.

Incubator.Slider – Added .hitSlop() to the RNGH Gesture.Pan() on the thumb, so the gesture handler natively recognizes touches in the expanded hit area on Android.
Also added hitSlop to the Pan gesture mock in jest setup.

Changelog

Slider, Incubator.Slider - Fixed Android bug where touches near the thumb failed to start a drag.

Additional info

• MADS-4866
• React Native Gesture Responder System docs

[github-actions]

✅ PR Description Validation Passed

All required sections are properly filled out:

• ✅ Description
• ✅ Changelog
• ✅ Additional info

Your PR is good for review! 🚀

---

This validation ensures all sections from the PR template are properly filled.

[adids1221]

How to reproduce

Drop this into PlaygroundScreen.tsx and test on Android:

import React, {useState} from 'react';
import {Platform} from 'react-native';
import {View, Text, Slider, Switch, Incubator} from 'react-native-ui-lib';

const TAG = `[Slider-${Platform.OS}]`;

export default function PlaygroundScreen() {
  const [disabled, setDisabled] = useState(false);

  return (
    <View flex padding-20>
      <Text text60 marginB-20>
        Slider Debug ({Platform.OS})
      </Text>

      <View row centerV marginB-20>
        <Text text70 marginR-10>
          Disabled
        </Text>
        <Switch value={disabled} onValueChange={setDisabled}/>
      </View>

      <Text text70 marginB-10>
        Slider
      </Text>
      <View
        style={{width: '100%', height: 60, justifyContent: 'center'}}
        onTouchStart={() => console.log(`${TAG} - PARENT onTouchStart`)}
        onTouchEnd={() => console.log(`${TAG} - PARENT onTouchEnd`)}
      >
        <Slider
          value={30}
          minimumValue={0}
          maximumValue={100}
          disabled={disabled}
          onSeekStart={() => console.log(`${TAG} - Slider - onSeekStart`)}
          onSeekEnd={() => console.log(`${TAG} - Slider - onSeekEnd`)}
          onValueChange={(v: number) => console.log(`${TAG} - Slider - onValueChange: ${v.toFixed(1)}`)}
        />
      </View>

      <Text text70 marginT-40 marginB-10>
        Incubator.Slider
      </Text>
      <View
        style={{width: '100%', height: 60, justifyContent: 'center'}}
        onTouchStart={() => console.log(`${TAG} - PARENT onTouchStart (Incubator)`)}
        onTouchEnd={() => console.log(`${TAG} - PARENT onTouchEnd (Incubator)`)}
      >
        <Incubator.Slider
          value={30}
          minimumValue={0}
          maximumValue={100}
          disabled={disabled}
          onSeekStart={() => console.log(`${TAG} - Incubator.Slider - onSeekStart`)}
          onSeekEnd={() => console.log(`${TAG} - Incubator.Slider - onSeekEnd`)}
          onValueChange={(v: number) => console.log(`${TAG} - Incubator.Slider - onValueChange: ${v.toFixed(1)}`)}
        />
      </View>
    </View>
  );
}

What to test

• Android — main fix: Touch near the thumb (not exactly on it) and drag → should start dragging immediately
• Both platforms — track tap: Tap anywhere on the track away from the thumb → value should jump to that position
• Both platforms — normal drag: Grab the thumb and drag → should work smoothly

[M-i-k-e-l]

You already have the default in the destructor

Suggested change

	.hitSlop(hitSlop ?? DEFAULT_THUMB_HIT_SLOP)
	.hitSlop(hitSlop)

I think this (modified) change along with changing the internal implementation from Slider to Incubator.Slider is enough (I think we've discussed testing the incubator version).
I've tested it on my device and it works, with that said I would not HF it and make sure it's fully tested (and also - please test on iOS)

[M-i-k-e-l]

If you do agree then also edit the description and changelog.
Either way please remove "React Native Gesture Responder System docs"

[M-i-k-e-l]

In the private screen - it seems that the video is no longer available, you can use a link from here IMO