Always translate home into meta+enter

[qbi-geny]

Description

JIRA: SYSTEM-2682

Home widget button is broken on ARM SaaS which uses a PaaS image, as desktop & paas images handle the home button differently.

First, the Android documentation for the actual mapping between linux keyboard keycodes and Android keycodes tells us:

• Linux KEY_HOMEPAGE (Qt::Key_HomePage) maps to Android KEYCODE_HOME and is the physical home button (back to "desktop")
• Linux KEY_HOME (Qt::Key_Home) maps to Android KEYCODE_MOVE_HOME and is

  "Used for scrolling or moving the cursor around to the start of a line or to the top of a list.

Historically, it seems that the desktop image maps KEYCODE_MOVE_HOME to KEYCODE_HOME, in device/genymotion/vbox86/Genymotion_Virtual_Input.kl, so the SaaS web player mapped the home widget to this button.

Now, the PaaS image does not have this mapping (it is not necessary), so the webplayer has an option to translate this button to Meta+Enter, which is a shortcut for the home button.

However, this results in the Paas in Saas configuration being broken, as the SaaS web player sends (ultimately, through webrtcd mapping & redis) the KEYCODE_MOVE_HOME to the PaaS image.

This fix:

• Removes the option, and always translate home into Meta+Enter as it's always a valid shortcut (tested Android 8-14).
  • This will require removing the option in web-ui.
• Changes the Keycode associated with the home widget button to KEY_HOMEPAGE, as it is more accurate, even though it ends up being translated. We could later remove the translation, when webrtcd is aware of this keycode.

Fixes SYSTEM-2682

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

• I've read & comply with the contributing guidelines
• I have tested my code for new features & regressions on both mobile & desktop devices, using the latest version of major browsers.
• I have made corresponding changes to the documentation (README.md).
• I've checked my modifications for any breaking changes.

[jparez]

The status is "draft", but does it still need to be reviewed ?

[qbi-geny]

Yes it is still draft, because so far I haven't managed to validate it works on SaaS.

[qbi-geny]

Finally managed to test it in example web player against staging SaaS ARM when based on #111