[Android] Guard update events to only be dispatched in ACTIVE state

[j-piasecki]

Description

1. Removes unused isFirstEvent
2. Adds a guard to ensure update events are only dispatched in ACTIVE state. I've noticed that dispatchHandlerUpdate was being called in state END.

Test plan

I didn't observe it in the runtime, only in the debugger while working on Touchable optimizations.

[Copilot]

Pull request overview

This PR refines Android gesture update dispatching in the core GestureHandlerOrchestrator by removing dead local state and preventing unnecessary update dispatch attempts after a handler has already transitioned out of ACTIVE.

Changes:

• Removes an unused local variable (isFirstEvent) in event delivery.
• Adds an explicit state check so dispatchHandlerUpdate is only invoked when the handler’s state is STATE_ACTIVE (in addition to the existing isActive guard).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.