Pixel Fingerprint Sensor shown as controller

Bug libgdx/libgdx#5596 is still presentn and is not solved: On a current Pixel 4a, the fingerprint sensor is shown as uinput-fpc device as reportd in MrStahlfelge/lightblocks#31

Our current code to detect if an input device is a controller:

gdx-controllers/gdx-controllers-android/src/com/badlogic/gdx/controllers/android/AndroidControllers.java

Line 312 in 9152086

    
           return ((device.getSources() & InputDevice.SOURCE_CLASS_JOYSTICK) == InputDevice.SOURCE_CLASS_JOYSTICK)

SDL's current code to detect is a bit different:

https://github.com/libsdl-org/SDL/blob/c59d4dcd38c382a1e9b69b053756f1139a861574/android-project/app/src/main/java/org/libsdl/app/SDLControllerManager.java#L118-L120

Before adapting SDL's solution, it is to check whether we get confused with TV remotes (https://developer.amazon.com/de/docs/fire-tv/identify-controllers.html#is-this-device-a-game-controller)

SDL will also report the fingerprint sensor as a controller, this is due to the fingerprint sensor reporting itself as such:

2021-05-18 16:53:30.648 17081-17135/com.badlogic.gdx.controllers.test D/Controllers: uinput-fpc
2021-05-18 16:53:30.650 17081-17135/com.badlogic.gdx.controllers.test D/Controllers: SOURCE_CLASS_JOYSTICK: 1
2021-05-18 16:53:30.650 17081-17135/com.badlogic.gdx.controllers.test D/Controllers: SOURCE_GAMEPAD: 0
2021-05-18 16:53:30.651 17081-17135/com.badlogic.gdx.controllers.test D/Controllers: SOURCE_JOYSTICK: 1
2021-05-18 16:53:30.652 17081-17135/com.badlogic.gdx.controllers.test D/Controllers: SOURCE_KEYBOARD: 1
2021-05-18 16:53:30.653 17081-17135/com.badlogic.gdx.controllers.test D/Controllers: SOURCE_DPAD: 0
2021-05-18 16:53:30.655 17081-17135/com.badlogic.gdx.controllers.test D/Controllers: KEYBOARD_TYPE: 1

This seems to be a bug of the fingerprint sensor itself, and there were a lot of complaints from players on other game engines as well. I suppose the other engines blacklisted the name "uinput-fpc" and suggest we do the same.