auto: increment master version to 15.0.33

change(web): adds error + console logs usable for Sentry reporting targeting #4797

fix(windows): avoid error if keyman32.dll renamed

Fixes #4939.
Fixes KEYMAN-WINDOWS-70.
Fixes KEYMAN-WINDOWS-71.
Fixes KEYMAN-WINDOWS-BR.
Fixes KEYMAN-WINDOWS-6J.

I am speculating a little here, because the root cause is not visible in
the crash report, but it appears that if keyman32.dll is renamed, that
the UnregisterControllerWindows function attempts to reload keyman32.dll
which means that (a) it no longer has a list of registered controllers,
and (b) it may fail to reload.

Instead of throwing an exception, we now only log this error in
development mode. The error is not likely to cause significant trouble
for end users as they are shutting down Keyman anyway at this point.

The resolution if there is any uncertainty during an upgrade is to
restart Windows. This is less than ideal but avoids file locks and
problems with in-memory DLLs. (Future versions of Keyman will schedule
upgrades to happen automatically after a restart before Keyman has been
started, in an effort to avoid this kind of trauma.)

fix(developer): chiral mismatch warning is disruptive

fix(developer): avoid crash if .kpj.user file is malformed

fix(windows): help contents broken from tray menu

fix(windows): access violation closing text editor

chore(windows): disable profile repair

fix(windows): crash when installing TIP in some rare situations

Merge pull request #4887 from keymanapp/fix/windows/4886-install-crashes-on-invalid-and-legacy-package-names

fix(windows): handle invalid package names during install

Fixes #4803.

This fixes part of #4803 - namely the obtrusive warning flagging that
there are mismatched modifier types in the keyboard. Instead of making
the change during tab switching, it simply shows a warning message in
the design view of the keyboard, which the developer can choose to
ignore.

This does not address the removal of comments or the switch of character
formats which is part of that conversion routine. That is a more complex
change to the parser.

auto: increment master version to 15.0.32

chore(linux): Remove experimental scripts

fix(linux): Don't crash on network problem (fixes #4911)

fix(linux): don't crash on legacy non-Unicode files 🍒

fix(android/engine): Don't set lexical model list to null

Follow-on to #4926

fix(android/engine): Change getList() to return an empty list instead of null

This prevents the NullPointerException in CloudRepository.prepareResourcesUpdateQuery() when the list doesn't exist.

fix(android/engine): Don't load woff fonts on Android N

Address review comments

Fixes #4874.

Opening product help from the tray menu would end up at a broken page.

Given the title of the link is "Help Contents", I have opted to open at
the help contents... (rather than the alternative of context/tray-menu).

Fixes #4848.

This error arose because the form was destroyed after kmshell.dpr
completes, which meant that sentry had already been destroyed. The
sentry call was simply to record a breadcrumb of the form being closed.

The fix is to move the lifecycle of the form into the `OpenTextEditor`
function. `OpenTextEditor` is used only by `initprog.RunKMCOM` and so it
is safe to remove the ApplicationRunning path of the code, which
simplifies the lifecycle of the form.

Fixes #4917.

This updates `TProjectLoader` to use the same exception handling pattern
for loading the .kpj.user file as we use for the .kpj file.

auto: increment master version to 15.0.31

If the network is down or the server name can't be resolved we
shouldn't crash. This change logs an error instead.

If we encounter a legacy non-Unicode file we now simply ignore the
file instead of crashing.

This fixes #4876.

(cherry picked from commit 59c45c46)

chore(android,windows): Check in crowdin for Indonesian

chore(common): Update crowdin for French

Fixes #4893.
Fixes KEYMAN-WINDOWS-50.
Fixes KEYMAN-WINDOWS-4Z.

Profile repair was using legacy code for re-establishing Keyman TIP
profiles after they had been modified by a third party app or Windows.
However, with Keyman 14's new profile registration pattern, this is both
less likely to occur and also easier to resolve (just disabling and
re-enabling the keyboard should do it).

Thus, I have opted to disable the profile repair code as, with the way
it stands at present, it may well make things worse, even aside from the
crash, because of disparities between user and admin TSF settings.