Replaces the script building kmcomp-$version.zip in TeamCity. Will be
used for more automated keyboard testing shortly.

Means kmcomp-$version.zip will be available as an artifact in all test
builds.

@keymanapp-test-bot skip

auto: increment master version to 16.0.30

fix(web): ncaps rules not matching on touch 🔥

Fixes #6910.

Regression introduced in #6874 / #6849 (which themselves were improving
the Caps Lock situation).

Ensures that either `NO_CAPS` or `CAPS` is always set in the modifier
flags.

auto: increment master version to 16.0.29

fix(developer): add no-ops for symbol builds for components

Fixes the release build where we do `nmake symbols` for developer/src,
which was failing on calls to these two sets of components. (In
windows/src, the build structure is different due to an additional layer
of folders, so we end up with no `nmake symbols` call on the common
components).

chore(android): disable sendError for js errors

auto: increment master version to 16.0.28

fix(web): improve `console.error()` reporting

auto: increment master version to 16.0.27

fix(linux): Fix post-install script

feat(developer): add flick and multitap to touch layout schema and doc 🙊

feat(developer): .keyman-touch-layout schema for 15.0 🙊

Co-authored-by: Joshua Horton <joshua_horton@sil.org>

chore(developer): rename developer/js to developer/kmlmc 🎢

fix(developer): Show full version number

fix(web): Maintain separate Caps Lock states for touch and physical

fix(developer): readonly groups should never emit output

fix(developer): dist path for server 🎢

fix(web): properly binds 'suggestionApplied' event handler

auto: increment master version to 16.0.26

This change fixes the ibus-keyman post install script which
previously failed if for whatever reason `SUDO_USER` is not set.

Fixes #6893

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

chore(web): update readme

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