Fix nested pressable's event propagation.

[latekvo]

Issue:

Test case: 3 nested pressables
Actions: click, press for <500ms, press for >500ms
Expected behaviour: No propagation
Observed behaviour: Propagation for 500ms (until long press activates), then no propagation.

Cause:

Touch and non-active events disregard component's layer,
only state respecting component's level is ACTIVE.

Solution:

Create a component which activates immediately after pressing Pressable, capture that event and use it for state setting and callback calling.

Important:

This PR also performs a lot of de-cluttering work in the utils.ts file.
This is necessary due to the convoluted nature of the handled problem, it was especially important to me in this PR to be dealing with clearly labelled functions.

closes: #2980

[latekvo]

As of 7326626, both Android and IOS works thanks to View's onTouchStart which is identical to Gesture handler's onTouchStart except for stopPropagation() method which prevents events from reaching obstructed parent elements.

[latekvo]

Previously I described how InnerPressableEvent (formerly PressEvent) has a structure that looks like it should be recursive but isn't.

Namely:

type InnerPressableEvent = {
  changedTouches: InnerPressableEvent[];
  touches: InnerPressableEvent[];
  [...]
};

After further testing, View actually uses it's version of this type in a recursive manner, which isn't the case for the legacy Pressable.

Since recursiveness in this case is not forced - aligns with the type's structure, and does occur on other components using this structure I'd argue that this is a direct upgrade from the current state, and thus should be implemented onto Pressable despite lack of it's presence on the legacy component.

What do you think? (c.c. @m-bert @j-piasecki )

[m-bert]

Finally, the time has come