Input: Improve logging for keyboards and joysticks

[garbear]

Description

This PR contains improvements to input logging, needed to track down the remaining Android joystick bugs.

Motivation and context

Contains only the logging improvements broken out from #24604.

How has this been tested?

Tested as part of my RetroPlayer builds since January: https://github.com/garbear/xbmc/releases

What is the effect on users?

• Improved input logging

Types of change

• Bug fix (non-breaking change which fixes an issue)
• Clean up (non-breaking change which removes non-working, unmaintained functionality)
• Improvement (non-breaking change which improves existing functionality)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that will cause existing functionality to change)
• Cosmetic change (non-breaking change that doesn't touch code)
• Student submission (PR was done for educational purposes and will be treated as such)
• None of the above (please explain below)

[garbear]

@joseluismarti Do the android changes look OK to you?

[joseluismarti]

In NDK 26 some new codes appear (AKEYCODE_VIDEO_APP_n, AKEYCODE_FEATURED_APP_n and AKEYCODE_DEMO_APP_n) I don't know if they should be incorporated as well

I've checked that android_printf displays correctly the keycode and the translated string.

I haven't checked the button mapping part, but the concept is the same, I think it's good.

[garbear]

I've added the NDK 26 keycodes as a separate commit. Jenkins build and merge.