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

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

chore(web): update readme

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

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

- About dialog
- Welcome screen
- Installer
- kmcomp help
- kmconvert help
- kmanalyze help
- kmdecomp help

This should help when testing to verify that we are testing the right
version.

Also fixed the keymansentry path when running command line C++ programs
from source repo.

Fixes #6799.

Caps Lock state management for touch layouts was not quite right -- it
touched the base Caps state variables rather than just the event Lstates
property. This meant that it was impossible to track the physical Caps
Lock key separately to the touch layout layer, and that the two states
would interfere with each other.

Fixes #6859.

The production path needed to have all files under the build/dist/
folder, not just the build/ folder. Broken in the refactor in #6630.

Fixes #6799.

For KeymanWeb compiled keyboards, readonly groups should never emit any
output. Rules in these groups permitted only to:
  * `use` other readonly groups
  * `call` external functions (which MUST NOT emit output)
  * `set`, `reset` or `save` store values

The base kmx compiler does emit output for rules in readonly groups.
Thus, the KeymanWeb compiler, when it transpiles from the generated
.kmx, needs to omit output for any readonly group, while avoiding any
other potential change in behaviour.

Fixes #6799.

For KeymanWeb compiled keyboards, readonly groups should never emit any
output. Rules in these groups permitted only to:
  * `use` other readonly groups
  * `call` external functions (which MUST NOT emit output)
  * `set`, `reset` or `save` store values

The base kmx compiler does emit output for rules in readonly groups.
Thus, the KeymanWeb compiler, when it transpiles from the generated
.kmx, needs to omit output for any readonly group, while avoiding any
other potential change in behaviour.

auto: increment master version to 16.0.23