instead of onclick + keypress. This allows for a smoother control for
situations where holding a button down is handled (as a test case,
check the Retaliate Roku Game, or scrolling through videos on YouTube
and moving through a video replay).

Even the main Roku menu uses rew/ff buttons as PgUp/PgDn alternatives
to skip options by screenfulls, and changing the behaviour of the
buttons here has an impact too. Same case for back in standard
navigation.

So, this is the only behaviour for buttons that emmit key events now.

with a fallback for old platform versions.

Also, new private getVibrator and code factorization to avoid
repetition between the new provideHapticEffect and
provideHapticFeedback.

to allow for haptic feedback just as the button is touched instead of
at the end on the click process, and to allow for the click process to
be prevented so that finer keyup and keydown commands can be sent to
the Roku while preventing a duplicitous keypress to be sent at the end
of the interaction. A click/keypress can still be used in case the
button is "clicked" by different means than touch input.

VIBRATE_DURATION_MS reduced to 25ms, and provideHapticFeedback calls
were replaced with provideHapticEffect with EFFECT_TICK for a more
subtle vibration pattern.

with VibratingImageButton, as the RepeatingImageButton behaviour is no
longer needed: finer keyup/keydown commands sent on touch events
render the timed keypresses obsolete. All buttons, including the dpad
can be implemented with VibratingImageButton directly.

RepeatingImageButton class no longer needed.

All buttons have their listeners configured with linkButton, which
sets up click and touch listeners.

just to respect the original order of the code.

as it doesn't make sense to do so, and this prevented special buttons
such as Power from working