chore(deps): autoupdate (needs claude fix)

[github-actions]

The dependency autoupdater failed during builds-and-checks.

Run log: https://github.com/siarheidudko/firebase-engine/actions/runs/29620176791

A Claude session has been dispatched to push fixes onto this branch
so the following commands all exit 0:

  npm run lint
  npm run build
  npm run cov

Claude will leave a status comment on this PR when it finishes.
PR-checks will re-run on each new commit.

[claude]

Status: no fix needed, no commits pushed.

What failed initially: The autoupdater's npm run update step failed with an ERESOLVE conflict (typescript@7.0.2 vs. typedoc@0.28.20's peer requirement of typescript@5.0.x–6.0.x). That failed bump was never committed — the autoupdater fell back to a "partial update" and this branch only contains the clean firebase-admin bump (^14.1.0 → ^14.2.0) in package.json/package-lock.json. typescript stays at ^6.0.3, so the conflict that broke the run isn't present in this branch's diff.

Verification performed (this sandbox):

• npm ci --no-audit --no-fund → exit 0
• npm run lint → exit 0
• npm run build → exit 0
• npm run cov → exit 1 in this sandbox, but not for a code reason: firebase-tools 15.22.4 (unchanged in this diff) requires a JDK 21+ runtime for the Firestore/Auth/Storage emulators, and this sandbox's Java is older with no permission available to me here to install/upgrade a JDK or use sudo apt-get. This is an environment limitation of my sandbox, not something introduced by the firebase-admin bump — firebase-tools's version is untouched by this diff, and the same failure would occur on master in this same sandbox. The real pr-checks/build-and-test GitHub Actions workflows explicitly set up JDK 21 via actions/setup-java@v5 before running tests, so they should be authoritative for the coverage check.

Changes made: none — no compatibility shims were required since the committed diff (firebase-admin bump only) installs, lints, and builds cleanly. No commits pushed.