Give xbmc::wayland::Keyboard the responsibility of managing the keymap.

The fact that we recieve the keymap as a string in shared memory is
really a wayland-specific implementation detail and not an abstraction
suitable for KeyboardProcessor. All KeyboardProcessor needs to care
about is receiving a keymap of some sort.
Do a reverse lookup on the keymap instead of hardcoding keys
Add key repeat tests