This error has been logged for every start of Keyman Engine for Web in
embedded contexts, but nothing bad ever happens. It does not really seem
to be anything we need to worry about. (It may be that the
`setDefaultKeyboard()` call will never return true, but it is still
harmless in any case.)

The back story:

Currently Keyman for Android reports errors sent to the console via
`console.error()` into Sentry but sentry-manager itself does not. This
means that Keyman for iPhone and iPad and other users of sentry-manager
do not report these errors. Many of these errors are important.

What's worse is that Keyman for Android's error reporting here (via the
`sendKMWError()` function in Keyman Engine for Android) does not capture
stack traces, and so many of the errors we get do not have enough
information to resolve them.

Furthermore, by having `sendKMWError()` in Keyman for Android, we
capture exceptions and other program errors twice -- once on the web
side, and once on the Java side -- this adds noise to our error
reporting. Sentry also tends to lump many unrelated `sendKMWError()`
events together, so tracking resolution to the errors is painful.

The fix:

This adds a patch to sentry-manager to capture `console.error()` and
`console.warning()` events and report them through Sentry's normal error
reporting, and disables the `sendKMWError()` report (although we leave
the breadcrumb in place for when there are later, related Java errors).
There is a Sentry integration called CaptureConsole, but it does not
support capturing stack traces until v6.14
(https://github.com/getsentry/sentry-javascript/pull/4034). Updating
Sentry to 6.14 or newer is a bigger job (due to ES6 baseline req. etc.)

Note that Keyman for iOS currently has some other stubs in place
overriding the `console.*` functions. These should be removed for
release builds, so that we can use this pattern instead. I will try and
tackle this in a follow-up PR (I will build it on my mac so I can test
it).

A sample error report captured with this mechanism (no sourcemaps here
because this is a -local build):

https://sentry.io/organizations/keyman/issues/3401287467/events/c40fd2cebb7743cc8dfe72e0dd34bf65/?project=5983524

I am proposing we back-port this to 15.0-stable as we are missing a lot
of data in many of our error reports on Android.

auto: increment master version to 16.0.25

fix(windows): show full version number

fix(common): trigger builds correctly for stable builds

auto: increment master version to 16.0.24

fix(web): null-guard for refreshLayout

fix(web): clears repeating bksp on keyboard reload ⬅️

Updated various places in Keyman for Windows to show the full
VersionWithTag rather than the short version number we had been
previously showing:

- Support tab
- System Information, About dialog

auto: increment master version to 16.0.23

fix(ios): eliminates conditional height for banner image

auto: increment master version to 16.0.22

fix(linux): Catch KeyboardInterrupt 🍒

fix(linux): Deal with non-existing files 🍒

chore(ios): modernizes app-help's internals

auto: increment master version to 16.0.21

chore(web): shorten check/web/file-size check message

auto: increment master version to 16.0.20

chore(ios): log script actions and fixup export settings to avoid version being clobbered

When the user cancels km-config by pressing Ctrl-C we don't want
this to be reported on Sentry.

Fixes #6813.

(cherry picked from commit 978c24e2)

This change deals with files that are referenced in the keyboard
package but don't actually exist.

Fixes #6811.

(cherry picked from commit b837a7fb)

chore(deps): bump got from 11.8.3 to 11.8.5