feat(developer): support FollowKeyboardVersion in kmc-package

feat(common): kmx file reader

auto: increment master version to 17.0.93

Fixes #7340.

Removes the unused <Version> element from <LexicalModel> element in the
.kps schema. (This needs to be copied to api.keyman.com also.)

Updates compiler to check for <FollowKeyboardVersion> and read the
version data from the .kmx in that case.

Unit tests updated. Some of the fixtures were incorrect as they had
<FollowKeyboardVersion> set for model-type packages or packages that
contained no keyboards. Fixed.

Read a .kmx file into memory in Typescript. Currently only reads stores
from the file, as these are the most common things needed for other
processes. Will add support for reading other metadata and rules in
future when required.

refactor(developer): kmc-model to use `CompilerEvent`

refactor(developer): move comperr.h to kmn_compiler_errors.h

chore(developer): only run keyboards-repo tests for a full-test

fix(developer): kmc-package path reference

auto: increment master version to 17.0.92

Replaces the existing error reporting in kmc-model with CompilerEvent
style messages. Some of the existing error reporting was kinda nice, but
consistency trumps pretty here.

One downside at present is the global filename and line variables in the
model-compiler-errors.ts unit. This is fragile, and should probably be
refactored further in the future.

Where it made sense, I converted various throws into ModelCompilerError
instances. If it appeared to be an internal error, I left it as-is, but
the external API interfaces wrap all unknown exceptions and convert them
into a compiler error message, so these APIs (compileModel and
loadFromFilename) now have a guarantee that they will never throw.

At this point, all of the error messages in the model compiler are
unrecoverable -- they will halt the compile entirely. However, the
pathway is there to support recoverable errors through the normal
callbacks.reportMessage mechanisms.

The message-counting mechanism is currently missing from this, as it
belongs in the API consumer, rather than in the low-level reporting
infrastructure. This means that models with large numbers of warnings
are going to generate scads of messages for now.

Note that the _users_ of CompilerCallbacks are subject to change in the
future, once we have all the compilers using the callbacks.

Consolidates the two copies of comperr.h (they were identical) and
moves to a common folder. Updates all references to comperr.h, except
for one github commit ref.

If kmcmplib build includes the --full-test flag, then configure and run
tests that include pulling in the keyboards repo; otherwise skip all of
that.

This will require CI changes to run full tests, relating to #8361.

fix(android/engine): Fix resetContext calls when selection changes

chore(web): sets kmc-model as dependency of input-processor test action

feat(developer): warn if .kps file includes a non-binary .kvk file

feat(developer): add CompilerMessages support to kmc-package

refactor(developer): move shared test helpers into common

feat(developer): use new message infrastructure in kmc-kmn

feat(developer): add warning options to kmc

refactor(developer): move build activities

fix(developer): kmc no longer emits double file extension for models

fix(developer): kmc-kmn would abort build on warnings

auto: increment master version to 17.0.91

fix(developer): package editor no longer loses RTL flag for LMs

Relates to #8150.

Legacy .kmp compiler would transform xml-format .kvk files into a binary
.kvk file; now we want that to remain the responsibility of the keyboard
compiler, so we'll warn the few users who are still doing this.