fix: Fix incorrect handling of unhandled MotionEvent axes on android (#74)

This PR fixes an issue in the Android gamepads plugin where certain
MotionEvent axes
could be incorrectly reported as handled even when no value change
occurred.

Context:
- I am using a wheel controller on a GCS-type drone controller.
- Before this fix, when using axes that were not recognized by the
library,
  the plugin still returned `handled=true`, which made it impossible to
  choose between using Gamepads or a custom library for the same input.
- The current workaround required modifying MainActivity.kt to call both
  Gamepads and a custom input handler, which caused duplicate events.

Changes:
- onMotionEvent now returns `false` if no supported axis has been
processed.
- Ensures unhandled axes can be caught by custom logic, preventing
duplicate
  values when integrating with other input systems.

Impact:
- Existing joysticks and gamepads continue to work as before.
- Provides more accurate and flexible event handling for apps consuming
  gamepad input.

---------

Co-authored-by: David Linhares <[email protected]>
Co-authored-by: Lukas Klingsbo <[email protected]>

Author: 3 people

packages/gamepads_android/android/src/main/kotlin/org/flame_engine/gamepads_android/EventListener.kt

@@ -44,10 +44,13 @@ class EventListener {
     }
 
     fun onMotionEvent(motionEvent: MotionEvent, channel: MethodChannel): Boolean {
-        supportedAxes.forEach {
-            reportAxis(motionEvent, channel, it)
+        var handled = false
+        supportedAxes.forEach { axis ->
+            val axisHandled = reportAxis(motionEvent, channel, axis)
+            if (axisHandled) handled = true
         }
-        return true
+
+        return handled
     }
 
     private fun reportAxis(