Fixes #7628.

Indy components do not treat URLs as UTF-8. Our legacy EncodeURL
function (sourced from Indy components) was the same. Discovered we
needed to fixup the parsing of URLs as well as the construction of them;
there may be other places we need to fix, although I did do a search for
the relevant types in TIKE source.

auto: increment beta version to 16.0.98

fix(mac): replace white background keyman system menu icon with transparent one

fix(developer): tweak captions for consistency

fix(windows): include debug info in kmshell build

fix(android/app): Don't show "Get Started" after setting Keyman as default system keyboard

auto: increment beta version to 16.0.97

fix(android/engine): Handle parsing empty JSONArray as JSONObject

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

feat(web): Custom layer targets for Shift double-tap

fix(common): always define dry_run variable

fix(android/app): Add check if bundle to PackageActivity is null

Applies proposed feature https://community.software.sil.org/t/testing-caps-on-touch/6849/5:

1. A `caps` layer must still exist in the keyboard.
2. If there is at least one multitap subkey defined on the Shift key on
   the active layer, then the `nextlayer` property of the first multitap
   subkey for the Shift key will be used instead of the default `caps`.
3. This does not change the behavior of the Shift key otherwise.

For example, the following defines a valid multitap key on Shift on the
`rightalt` layer to switch to a custom extended `rightalt-shift-caps`
layer.

This does not implement any other multitap functionality. It just allows
the keyboard developer to specify a target layer for a given double-tap.

```
  {
    "id": "K_SHIFT",
    "text": "*Shift*",
    "width": 150,
    "sp": 1,
    "nextlayer": "rightalt-shift",
    "layer": "default",
    "multitap": [
      {
        "text": "",
        "id": "T_new_694",
        "sp": "1",
        "nextlayer": "rightalt-shift-caps"
      }
    ]
  },
```

Fixes #7605.
Fixes #7606.

fix(developer): handle high-bit-set HKL correctly

fix(developer): support gif preview images in Package Editor

fix(developer): Make Details and Build tabs scrollable

Fixes #7599.

MSKLC HKLs have high bit set, which means that we need to explicitly
cast from Integer to DWord to avoid range check errors.

auto: increment beta version to 16.0.96

Should allow us to get line numbers for kmshell.exe crash reports

fix(developer): publish `@keymanapp/keyman-version` to npm

Merge pull request #7585 from keymanapp/fix/developer/298-avoid-reformatting-unchanged-system-stores

fix(developer): avoid reformatting unchanged system stores

fix(developer): generate a default icon for basic keyboard projects

fix(developer): remove ancient samples

fix(developer): prevent repeated `begin` statements

fix(developer): ensure kmlmp handles paths

fix(developer): Use US base layout for debugger

Fixes #7582.

Because of https://github.com/npm/cli/issues/3466, we must publish our
internal dependency @keymanapp/keyman-version. This change adds a common
builder function builder_publish_to_npm in build-utils-ci.inc.sh to help
with that task, which should be adopted by other scripts that need to
publish to npm, in the future.

For now, responsibility for publishing keyman-version is delegated to
kmlmc. In the future, we will move this to a single top-level build
action that publishes all npm modules across the entire repo for the
given version.

Co-authored-by: rc-swag <58423624+rc-swag@users.noreply.github.com>

Fixes #6974.

GIF images were not supported in the Details tab, Image file, because we
didn't link in GIF file support. After linking it in, we also needed to
change over the picture rendering to have an intermediate render step,
as the existing model only worked with .bmp images.

At the same time, added warnings for wrongly-sized images to the image
size information.

Fixes #5238.

The Details and Build tabs have fixed positional content in the Keyboard
Editor, Model Editor, and Package Editor. Sizing the window too small
can cause content to be outside the bounds of the tab. This patch moves
these tabs into scrollboxes (except for Details tabs on Keyboard and
Model editors, which were already in scrollboxes). The remaining tabs
have resizable content. The tabs will still become fairly unusable if
they become too small, but this should be less of a problem than before.