fix(web): improve keyboard switch performance

fix(web): remove obsolete popupBaseTarget

auto: increment master version to 15.0.157

fix(windows): fix loadkeyboardoptions core memory error

auto: increment master version to 15.0.156

fix(web): clear longpress timeout if user does a flick up

fix(web): shorten setFocusTimer()

fix(web): reset scroll anchor on touchend

Co-authored-by: Marc Durdin <marc@durdin.net>

auto: increment master version to 15.0.155

chore(linux): Run ibus-keyman tests as part of the build 🎫

Part of #5613.

Array has to be NULL terminated.

Part of #5613.

chore(linux): Remove unused test methods 🎫

feat(mac): i18n, support localization of Keyman for Mac

LoadKeyboardOptionsCore no longer frees memory that
has not been allocated.

fix(web): inline osk keytip position

fix(web): simplify hide transition

Summary of these changes:

Two targeted improvements; more optimization is possible but IMO this is
a significant enough improvement to go through test:

1. In oskView.ts, avoid calling `VisualKeyboard.refreshLayout` twice
   from `OSKView.refreshLayout`. This roughly halves the time spent in
   `VisualKeyboard.refreshLayout` for a keyboard switch.
2. In modelManager.ts, we avoid a very expensive `unloadModel` /
   `loadModel` sequence from `registerModel` by checking to see if the
   model spec we are passed is already registered. This avoids an
   expensive callback to Keyman for Android which causes the banner to
   'bounce'.

Longer notes:

So `VisualKeyboard.refreshLayout` is called 20+ times during a keyboard
switch. It is a very expensive call. It is the bulk of the time spent
when you press the globe key in Keyman for Android. This seems ripe for
optimization; see the following functions in keyboard.html:

* `setKeymanLanguage` -> `setActiveKeyboard` -> 6 calls
* `enableSuggestions` -> `registerModel` -> 8 calls
* `stateChange` -> 6+ calls

`OSKView.refreshLayout` always seems to call
`VisualKeyboard.refreshLayout` twice: first with `setSize`, and then
again itself.

Keyman for Android and KeymanWeb seem to fight over who is responsible
for selecting models (KMW first calls `loadModel`, then Keyman for
Android calls `unloadModel`, `loadModel`, through `enableSuggestions`).

The fix for rotation (`correctOSKTextSize()`), as called from
`stateChange()`, is expensive as well, because it rebuilds the entire
keyboard from scratch.

Along with that, we have the size of the webview changing as the model
is unloaded and reloaded and lots of back-and-forth between the
KeymanWeb and KMEA which seems unnecessary.

Shouldn't KeymanWeb be responsible for loading and unloading models,
once they are all registered? We should only need to register the models
once at page load time (when config changes, do we just reload the
page?).

auto: increment master version to 15.0.154

fix(web): resolve unhandled exception in promise

auto: increment master version to 15.0.153

This change removes the pre-edit related test methods since we
don't use the pre-edit option.

Fixes #5950.

If a user starts a longpress gesture and then flicks up, that
immediately brings up the longpress menu, and the timeout for display of
the menu should be cancelled -- otherwise the end result is a key that
stays 'stuck' on.

Fixes #5912.

The variable `popupBaseTarget` is never set. Removing.

Fixes #5909.

The `setFocusTimer()` delay was 1000ms. However, it seems that a much
shorter delay accomplishes the same outcome for switching between
controls, as the important factor is to block asynchronously-arriving
events from cancelling the OSK / focus controls for touch alias
elements.

I have set the delay to 50ms. This is fast enough that a click in a
control followed by a click on the page area will always cancel the OSK,
but gives the space needed for queued focus/blur events have time to be
processed before cancelling the timer.

fix(common/core):  Update decxstr to check all characters while decrementing

auto: increment master version to 15.0.152