feat(android/app): Add menu to adjust keyboard height

auto: increment master version to 15.0.99

fix(linux): Fix lost context after pressing K_SHIFT 🚧

fix(ios): iOS 13 and 14 only - stuck settings toggles

fix(common/core/web): behavior with unmatched final group

chore(developer): hide debug events panel 🐞

fix(developer): get Test Mode working again 🐞

chore(developer): refactor forcekeyboard in debug 🐞

chore(developer): debug deadkey 1-based values 🐞

fix(developer): debugger cleanup 🐞

auto: increment master version to 15.0.98

fix(linux): Fix uploading to launchpad 📦

Follow-up of #5536.

auto: increment master version to 15.0.97

fix(windows): Welcome should always show in front

This fixes typing `n>` with sil_ipa keyboard which no longer output
the expected `ŋ` because pressing the shift key reset the context.

For modifier key presses we now exit `KMX_ProcessEvent::ProcessEvent`
early.

This change also removes a redundant line from engine.c. Clearing
the context happens in `reset_context()` again if necessary.

Fixes #5591.

chore(android): Remove runConfigurations.xml files

Relates to #5013.

Hide the debug events panel by default, and add
a Tools menu item to make it visible for dev purposes
(Ctrl+Shift+click on Tools menu to view).

Relates to #5013.

This resolves the broken Test Mode with Keyman Core. Previously, Test
Mode just dumped the keyboard into Keyman for Windows, and let it do its
thing. Given that we no longer have the dependency on Keyman for
Windows, the Test window must use Keyman Core to process keystrokes, and
that means there are some differences in how Test Mode operates in 15.0:

* Behind the scenes, the Test mode is just the Debug mode with
  breakpoints and single step disabled, and the Debug Status window
  hidden
* Test mode requires debug information in the keyboard (see note below)
* You can always switch between Test and Debug mode
* Deadkeys are always shown in the debug window

Test Mode now requires debug information to be included in the keyboard
in order for deadkeys to be tracked correctly in the editor. While it
would be possible to remove the need for this, it does not add any
significant benefit to do so -- doing so would mean that the tester
would have less visibility into deadkeys, and complicate the Core
marker tracking in the debug window.

I considered removing Test Mode altogether, but it still feels like a
useful view for playing with a keyboard without all the debugging
paraphernalia cluttering the display. It's a little slower than full
native Keyman for Windows (aka the 14.0 Test Mode), because the debug
hooks are still running in the background, but it is quite usable.

Note the removal of `Application.ProcessMessages`. This resolves the
issue of keystrokes being swallowed by the debugger during
non-interactive debug runs, making rapid input work properly in both
Debug Mode and Test Mode.

fix(windows): handle restoring modal dialogs consistently

fix(linux): Handle corrupt icon file

fix(linux): Check for valid kmp file

Relates to #5013.

Before starting on new functionality in the debugger, I wanted to
cleanup a bunch of bits and pieces, including:

1. Correct handling of text selection and deletion
2. Refactor of character grid at bottom of debug window
3. Deadkey realignment after text changes
4. Correct tracking of cursor position between events
5. Handling a few destruction edge cases

fix(android): removes duplicated line

fix(android): keyboard's black bar bug