Fixes #6788.
Fixes KEYMAN-WEB-22.
Fixes KEYMAN-DEVELOPER-BQ.
Fixes KEYMAN-ANDROID-160.

Fixes a crash introduced in #6473 which was trying to prevent modifier
keys from triggering "fat finger" alternate lookups, due to incomplete
nullish coalescing.

Related to this, from what I can see, a secondary side-effect of the fix
in #6473 was that some key events may have never had their ruleBehaviors
finalized if they matched the `isOnlyLayerSwitchKey` heuristic, leading
to potential issues with edge case 'deadkey+layer switch' keys or keys
that set store values, for example. So this fix also makes the
`isOnlyLayerSwitchKey` test more targeted.

Identified this when adding a Caps Lock layer to sil_euro_latin and
testing the layer switching. At time of fix, the error had been raised
in KeymanWeb, Keyman Developer and Keyman for Android, but not yet
Keyman for iPhone and iPad.

auto: increment master version to 16.0.14

chore: beta to master merge A16S4

fix(android): check index validity in getCurrentKeyboardInfo

chore(android): adds diagnostic logging to assist a fix for #6703

fix(web): row height layout calcs now consider layer-group padding

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

auto: increment master version to 16.0.13

fix(common): update increment-version for new tsc, node versions 🎡

* Addresses some Typescript-specific breaking changes in destructured
  types.
* Removes npm version calls and package*.json updates -- these are no
  longer required.
* Adds resources/build/version as a workspace to root package.json.
* Runs `npm ci` on the repo root for resources/build/version.
* Adds additional logging.

chore(web): replace lerna with npm workspaces and ts projects 🎡

auto: increment beta version to 15.0.260

change(web): browser test timeout tweaks

change(web): adjusts minimum distance needed for quick-display of subkeys

fix(windows): Install TIP crash with inconsistent bcp47tag

fix(android/engine): Disable haptic feedback on hardware keystrokes

The BCP47tag is canonicalized in GetUserDefaultLanguage.
Comments updated for the function to make developer aware.

Comments added to GetKeyboardLanguage to make clear that it
can actuall Add/Set a langague in the com object.

auto: increment beta version to 15.0.259

fix(web): fixes OSK-interaction issues in Float, Toolbar UI modules 

chore(web): switch on additional BrowserStack reporting

chore: add 14.0 entries to beta HISTORY.md

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

Per support case with BrowserStack, am turning on deeper
reporting for BrowserStack-based testing in karma.

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 beta version to 15.0.258