The event interpreter should intervene later, after decoding.
Decoding should happen first, and then the Event should
be passed to the InputLogic.

For the time being, we will leave the (unused) EventInterpreter
class and its friends, because we'll use them again later.

Bug: 13406701
Change-Id: I7582d486724311e39e6692e606cca50c78800643

Change-Id: I1c5b27c8edf231680edb8d96f63b9d04cfc6a6fa

Bug: 5037589
Change-Id: I9e1ff92df7d0c58eb7a0f33603adebc9efb86585

Change-Id: If2fe6f0f4f88a6ae1f22664ded61cec6942c18b9

Change-Id: I750a07c0c564a95ceac734afa873ca3da9626a7f

Essentially this does activate auto-correction with a hardware
keyboard, although a lot of things are still left to implement.
No proximity is used yet which means only missing and excessive
letters are considered. Dead keys are not handled. No combiner
is supported. No suggestions are displayed. Resuming suggestions
does not work correctly with a hardware key (because the view
holds a temporary hardware event 'onKeyPreIme' and the event
from the IME won't be handled until this is handled which won't
happen until after the IME said that it did handle the event).

Bug: 5037589
Change-Id: Idcb5c7b26d56717ed772d53c062362807f11cdae

Bug: 5037589
Change-Id: I0a4926f94ef8d1caa17669801608608648b697b9

Bug: 5037589
Change-Id: Id8eea0e2bd00dd339a1efb4b0542e4c091a84195