[General] Fix onBegin not being called when the native recognizer skips the BEGAN state

[j-piasecki]

Description

The current state machine implementation allows for onBegin callback to be skipped if the native recognizer goes from UNDETERMINED directly to ACTIVE state (which is a valid transition in some cases).

This PR updates the logic to "backfill" the onBegin callback when receiving the UNDETERMINED -> ACTIVE transition, before calling onActivate.

Note: this PR only changes the behavior for the V3 API. I'm not sure whether it should be backported to V2 as it would likely be a breaking change.

Test plan

This scenario:

react-native-gesture-handler/packages/react-native-gesture-handler/src/components/GestureButtons.tsx

Lines 67 to 68 in 59a5311

	// NativeViewGestureHandler sends different events based on platform
	state === (Platform.OS !== 'android' ? State.ACTIVE : State.BEGAN) &&

[m-bert]

this PR only changes the behavior for the V3 API. I'm not sure whether it should be backported to V2 as it would likely be a breaking change.

Did we have such issues before? While it seems important, I don't think we have to backport it atm.

---

Also, I've just noticed that this whole machine is one if ... else ... and nothing more below. We could "refactor" it at least to use early returns, maybe it would be a bit easier to read. But of course it's not the scope of this PR, so I can do it later.