Merge pull request #6706 from keymanapp/fix/android/cherry-pick/getKeyboardInfo-with-invalid-index-6703

fix(android): check index validity in getCurrentKeyboardInfo 🍒

This fixes crash reported as #6703. This issue was first reported in
14.0.282-stable. I have done a careful review of changes in 14.0.282
(and 14.0.281) but have been unable to find any changes that could have
bearing on this.

The basic issue is that there appears to be some circumstances where
`KMManager` thinks that it has a keyboard loaded (ref
`SystemKeyboardLoaded` variable), but `KMKeyboard.currentKeyboard` is
still `null`.

The crash has been reported for only a very small set of users, 119 at
time of fix, but average reports per user is over 100. As is usual with
this type of thing, a small fraction of those users are reporting the
majority of crashes. I have not found any real commonality across the
error reports -- they are geographically dispersed, across multiple
device types and Android versions.

Note that this addresses the error at hand but as I am unable to
reproduce the issue, does not necessarily address the root problem, so
there may still be other issues reported even after this is fixed.

A longer-term refactor would eliminate `SystemKeyboardLoaded` because
from what I can tell, we should always be able to determine that from
the state of `KMKeyboard.currentKeyboard`. However, the state
entanglement is a lot deeper than just those two variables, with cross
references to keyboard indexes between `KMManager` and `KMKeyboard`
which need to be resolved (`KMKeyboard` should *never* refer to
`KMManager`).

auto: increment stable-14.0 version to 14.0.295

fix(web): crash in highlightKey

Fixes KEYMAN-WEB-X

auto: increment stable-14.0 version to 14.0.294

fix(windows): unbreak keyboard install

#6648 introduced logging around keyboard install. Unfortunately, a
code formatting issue meant that it introduced a bug causing all
elevated installs to fail. This fixes that and tweaks the logging.

auto: increment stable-14.0 version to 14.0.293

fix(windows): sentry debuglogging for DoInstall

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

This commit adds some sentry logging to the TTIPMaintenance.DoInstall
to assist in tracking bug with installing a TIP for new language
associated with a Keyboard.

auto: increment stable-14.0 version to 14.0.292

fix(windows): put correct HK_ALT flag for modifier 🍒

Merge pull request #6506 from keymanapp/fix/windows/cherry-pick/6504-access-violation-logging-tip-maintenance

fix(windows): don't log before checking nil when installing keyboard 🍒

auto: increment stable-14.0 version to 14.0.291

chore(oem/fv/android): Update dependencies 🍒 

auto: increment stable-14.0 version to 14.0.290

fix(web): track load error detail 🍒

This is a follow-up for #6331. We still did not have enough detail to
be able to trace the root cause of the load errors. This adds a little
more diagnostics.

chore(android): 🍒 Update Play publishing plugin to 3.5.0 and other plugins

fix(mac): invalid keyboard breaks configuration

fix(android/engine): Test fileVersion during package install 🍒 

Fixes #4877.

If a keyboard is invalid for any reason (missing, wrong version),
then it would not appear in Configuration, which would break the
row indexing, causing crashes.