fix: ios snap behaviour

[andreialecu]

On iOS, onMomentumEnd is not called unless the user is scrolling with momentum.

This ensures that the snap logic is called properly when momentum scrolling is not in use.

Additionally, it reenables overscroll/bouncing the scroll view.

Fixes #59

[andreialecu]

Note that I didn't test Android at all, so please test before merging.

Also in the DiffClamp + Snap Example, it seems to snap over the article tab covering it. But I'm not sure if this is a bug introduced by this PR or not. It works fine on the last tab where there's more content:

Recording: https://streamable.com/gqfbbd

[andreialecu]

Longer video that shows things working (besides #66): https://streamable.com/nez289

[andreialecu]

A comment on 05ea6af (#65):

https://docs.swmansion.com/react-native-reanimated/docs/next/api/useAnimatedReaction/

I believe using the empty array fixed some small jittering in the diffclamp demo.

I noticed there are other usages of useAnimatedReaction that don't define a dependency array. Those may need optimizing too (in a separate PR)

[PedroBern]

Also in the DiffClamp + Snap Example, it seems to snap over the article tab covering it. But I'm not sure if this is a bug introduced by this PR or not. It works fine on the last tab where there's more content:

I saw it in other recordings, it's weird, here is fine

I noticed there are other usages of useAnimatedReaction that don't define a dependency array. Those may need optimizing too (in a separate PR)

I will review it

[alexpchin]

Hi, @andreialecu and @PedroBern. I've just pulled this and ran as per https://github.com/PedroBern/react-native-collapsible-tab-view/issues/59#issuecomment-770209467 I can confirm that the Snap is fixed but think we can achieve without setTimeout?

[PedroBern]

closed in favor of #67