[oristanovic]

What do these changes do?

Run typecheck, lint, tests and a release-mode bundle on every pull request, in
their own job, and update the native job's toolchain.

Why are these changes necessary?

CI ran npm ci and two Debug native builds. A Debug build loads its JavaScript
from Metro at runtime, so the JS was never compiled or bundled, and typecheck,
lint and tests were never invoked at all. Broken JavaScript could not fail a
build — which is how the example's missing imports went unnoticed.

How did you verify these changes?

From a real install in a clean worktree: typecheck reports no errors, lint
exits 0, and the bundle writes. npm test fails here because the suite is
#785.

Anything else a reviewer should know?

Two things had to be fixed before the gates could go green, and both are worth
a look on their own.

example/src/AirshipConfig.ts holds credentials and is gitignored, so the
example could never typecheck or bundle in CI. The committed
AirshipConfig.ts.example is copied into place.

The example imported @react-navigation/native, @react-navigation/stack and
@react-native-clipboard/clipboard with nothing declaring them in either
package.json and zero entries in the lockfile. They resolved only from stale
node_modules in a long-lived checkout, so a fresh clone could not typecheck,
bundle or run the example. They are declared now, together with the two native
peers @react-navigation/stack needs.

The example's typecheck backlog is cleared here too. One of those was a defect
rather than a type complaint: addCustomEvent was passed
properties: undefined, and CustomEvent requires that field.

Stacked on #786, which the lint step depends on, and merged in already to keep
the example edits from conflicting. Merge #785 first so npm test exists.

Making the four checks required on main is a branch protection setting, not
part of this change.

🤖 Generated with Claude Code