chore(android/engine): Don't show Toast errors on stable tier

chore(linux): Update debian changelog 🍒

chore: Update history-and-versioning to match history

chore(linux): Update whatsnew

Co-authored-by: Eberhard Beilharz <ermshiperete@users.noreply.github.com>

auto: increment beta version to 16.0.100

(cherry picked from commit 3b3d4e9e)

fix(core): emit keystroke was writing to wrong queue

fix(core): `save()` should be on internal kmx action queue

Merge pull request #7659 from keymanapp/fix/developer/7658-handle-unpaired-surrogate-in-token-command

fix(developer): handle unpaired surrogate

fix(developer): handle crash reports without Keyman Engine installed

fix(developer): handle shutdown cleanup more cleanly

fix(developer): handle edge cases for app sources

fix(web): Add polyfill for Array.findIndex()

fix(web): Add polyfill for Array.includes()

Fixes #7658.

When manipulating text that contains an unpaired surrogate, the text
editor could throw an exception trying to encode the text to send
through to the token command. This simply masks that error.

Fixes #7656.

If Keyman Developer is installed, but not Keyman for Windows, then
tsysinfo.exe is not present. If a crash occurs, this causes a secondary
crash when trying to display the error handler dialog. In this
situation, we now just show a dialog box with a short message rather
than the more friendly dialog available via tsysinfo.exe.

We could consider adding tsysinfo.exe into Keyman Developer for a future
release.

Fixes #4757.
Fixes #6928.

Three separate ways shutdown is more robust:

1. Destroy main form before web server -- this ensures that all main
   form routines have deregistered app sources from web server.
2. In some situations, `FormClose` can be skipped by shutdown routines,
   for example, if you call `Application.Terminate`. This change ensures
   that we get a second chance to cleanup in the form destructor with
   `DoCloseCleanup`.
3. In the Online Update Check, instead of `Application.Terminate`, we
   now use `Application.MainForm.Close`, which is much more polite, as
   it ensures that changed files are saved, etc, and does proper
   cleanup. This particular change may make the other two somewhat
   irrelevant but they are still sensible as they will cover us for
   other potential form destruction sequences.

Relates to #6928 and KEYMAN-DEVELOPER-74.

Fixes one more potential pathway for assertions being raised, and adds
some extra debugging in case there are additional pathways we are not
capturing.

auto: increment beta version to 16.0.99

fix(developer): improve support for inferred key cap text

fix(web): avoid reset for touch system keyboard

fix(developer): kmlmc has runtime dependency on keyman-version

fix(web): Handle undefined keyId in multi-tap

Fixes #7649.

emit_keystroke code path in kmx processor was writing directly to the
core queue instead of to the internal kmx processor queue. This caused
it to be out-of-order in the actions sent to the engine/debugger.

Engines didn't really care but it broke the debugger, for example if
only a deadkey was in the buffer and backspace was pressed, Developer
would assert as it would get unexpected context for the deletions.

Fixes #7647.

fix(developer): disable Keyboard|Compile if no project loaded

fix(developer): prevent exception in charmap when unable to focus

fix(developer): handle EEncodingError loading text file

chore(developer): tidy up compile hints

fix(developer): update monaco editor to 0.15.6