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

chore(windows): add unit test for SetupCoreEnvironment

auto: increment beta version to 16.0.105

chore(android/engine): Add more logging for keyboard restart

auto: increment beta version to 16.0.104

refactor(linux): Use consts instead of strings

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

fix(windows): check if permissions for thread to access file

chore(windows): include debug info in keyman build

chore(windows): Add safecall for internal CustomisationStorage API interface

fix(windows): handle timeout in downloads

chore(windows): add sentry traces for unsolved crashes

fix(windows): click in 1 pixel high box in Language Switch window caused crash

Same as #7600, but for keyman.dpr.

Fixes #7708.

This makes it easier to track what is happening for errors where
otherwise we found that exception messages were being cropped; for
example, see KEYMAN-WINDOWS-X.

The error messages were being cropped because the exception handler was
in the exe module, but the exception was being raised in kmcomapi
module. When the exception was handled, the handler tested to see if
the exception object inherited from exemodule.Exception, but it was
inheriting from kmcomapi.Exception instead, and so it did not attempt
to load the message detail.

By adding `safecall` calling convention to `KeymanCustomisation`, we
move responsibility for handling the exception to the
`TKeymanAutoObject.SafeCallException` function, and we get full detail
for the exception.

Adds Sentry breadcrumbs for the following crash reports:
* KEYMAN-WINDOWS-62
* KEYMAN-WINDOWS-6H (? no reports in recent releases, so may be
  resolved)
* KEYMAN-WINDOWS-7J
* KEYMAN-WINDOWS-4R

The source of these crashes is hard to pinpoint, so hoping that this
additional data sheds some light.

auto: increment beta version to 16.0.103

chore(android/app): Remove debugging info on build.gradle

fix(android/app): Append tier to app name

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

Fixes #7698.

Due to a `>` instead of a `>=` check, there was a one pixel high box at
the bottom of each list of input methods for each language which would
reuslt in an invalid value for `FNewHoverKeyboard`
(`lang.KeyboardCount`).

As well as fixing this, I changed the result for clicking below the
input method list to the more logical last item in the list rather than
the first.

fix(windows): make sure IdStackWindows finalizes after Vcl.Forms

auto: increment beta version to 16.0.102

chore(linux): Update Debian standards version

chore(linux): Update debian changelog 🍒

fix(linux): Fix keyboard icon in system tray