chore: fix version increment for force parameter

chore(common): version 15.0 release tweaks

chore: stable version

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 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
...

auto: increment beta version to 15.0.258

fix(developer): install keyboard call should quote kmshell.exe path

fix(developer): kmcomp package compiler race condition

Fixes a race condition when compiling multiple packages, where the
temp path may be re-used before the compiler has finished with it.

To take advantage of this fix, I wanted to make sure I was using the
right kmcomp.exe when building unit tests for Keyman Core. This
uncovered a couple of other things:

* Updates Keyman Core build infrastructure to use the current kmcomp.exe
  rather than a system-installed one.
* Corrects a bug that was identified by the 15.0 version of kmcomp in
  one unit test (duplicate `&NAME` stores -- the meson test script
  prepends a `&NAME` store to each source file during build).

@keymanapp-test-bot skip

auto: increment beta version to 15.0.257