auto: increment master version to 17.0.209

fix(linux): Fix trigger for baseline tests

chore(linux): Fix GHA triggering

fix(linux): Fix baseline tests

When the baseline tests change we want to trigger a Linux build.

Change the test to use characters in the context that don't appear in
the keyboard.

When we build a PR on TC we use `pull/ID/head` for the build, not
`pull/ID/merge`, i.e. the tip of the feature branch and not a merge
with the base branch. This means that during the build `pull/ID/merge`
is unknown. This change modifies the trigger to use `pull/ID/head` for
GHA builds as well.

It's still a mystery why `pull/ID/merge` was known to builds in most
cases but failed for some PRs.

fix(web): Ignore `osk-always-visible` on non-desktop devices

fix(web): Fix clearing of deadkeys

auto: increment master version to 17.0.208

feat(developer): Add more non-printing characters

refactor(web): Link to `index.html` in test pages

This change adds `index.html` to all links that point to test index pages.
This will show the index page instead of the directory listing when
opening locally, identical to the behavior on TC.

Fixes #9918.

auto: increment master version to 17.0.207

Addresses code review comments.

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

fix(developer): resilience in loading Server config and cache files

fix(developer): Sentry in Server should honour reporting settings

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

Fixes #8568.

Also adds a similar testcase to the baseline keyboard tests.

Since things are working in both cases it seems that the problem got
fixed and the comments are obsolete.

feat(developer): provide line number for some kmw compiler messages

chore(common): remove prepublish step from package.json

chore(developer): remove compile.pas and CompileErrorCodes.pas

Merge branch 'fix/developer/9939-sentry-support-in-server' into fix/developer/9848-resilient-cache-state-loading

Fixes #9848.

Root cause of #9848 is unknown, because the cache state file was filled
with nul bytes. It is unclear how that could have happened, but seems
likely to be external interference.

The cascade was that Server failed to start because it would crash when
attempting to load the cache state file. So this fix resolves that by
handling invalid file exceptions.