The build agent already has the relevant `SENTRY_` environment variables
set in order to complete builds for all projects. Thus, we should
exclude these values from the xcode build. However, we need to ensure
that the `SENTRY_URL` and `SENTRY_ORG` variables are imported into the
xcode environment from the build agent environment.

fix(common): Fix cherry-pick labeling (🍒)

My previous commit escaped the parens which should be part of the
regex.

(cherry picked from commit 01789142)

chore(common): Enhance cherry-pick labeling 🍒 

fix(linux): Fix debian package script 🍒 

chore(linux): copy Keyman for Linux 15 reference to 14

So far we only check for the 🍒 emoji character to add
the cherry-pick label. GitHub now also supports emoticons as text
in PR titles. This change adds the detection of the `🍒`
text.

(cherry picked from commit cf9cdf86)

(cherry picked from commit 1fd26dcf)

km-config in version 14 has slightly different parameters. This
change regenerated (and hand-massaged) the reference help file
for 14.0

chore(windows): fix broken links in help 🍒

As we auto-generate the reference docs for 15.0, but not 14.0, let's
just copy the version 15 docs into 14 so we have them available online.

Query: are the docs accurate for 14.0 or have options changed?

auto: increment stable-14.0 version to 14.0.283

fix: help.keyman.com script file cleanup

chore(mac): Add help links for installing Keyman and keyboards 🍒 

fix(mac): add support for M1 processor 🍒

Fixes #5700.

Adds support for arm64 (M1) to textinputsource in the Keyman app. All
other executables are already fat with support for both x86_64 and
arm64.

auto: increment stable-14.0 version to 14.0.282

fix(windows): fallback to filename if `&name` not set 🍒

fix(common/core/web): Remove empty rows in OSK 🍒 

test(windows): investigate TIP crash

Fixes #5683.

If `store(&name)` is missing from a keyboard, then fallback to the
filename of the keyboard (sans extension). This fixes a regression in
14.0 keyboard registration.

I opted not to make this change in kmxfile but rather in places which
use it in the Keyman Engine COM API, because I wanted kmxfile to remain
truthful about all details of what it is reading from the file.

Given that the COM API will now never return an empty string for the
name of the keyboard, there are  mitigations for this in Keyman
Configuration which are unnecessary, but it is not harmful for them to
remain there.

Will cherry-pick to stable-14.0.

Merge pull request #5677 from keymanapp/fix/developer/cherry-pick/5577-import-from-layout-dirty-flag

fix(developer): ensure file modified after import from layout 🍒

chore(common): report-history 🍒

Relates to #4889.

Adds extra diagnostics to try and trace why we are getting a crash in
rare cases when installing a keyboard language.

Effective cherry-pick of #5527, #5603, to bring report-history.sh into
the stable-14.0 tree for reporting purposes and consistency.

Fixes #5577.

This ensures that the touch layout file is marked as modified after
running Import From Layout in Keyman Developer, so that changes are
not lost when you save.

fix(android/engine): Fix backspace on Android 5.0 🍒 

fix(linux): Use first keyboard language if none given 🍒

fix(web): Fix layers for embedded longpress keys

Co-authored-by: Joshua Horton <joshua_horton@sil.org>