chore(deps): autoupdate (needs claude fix)

[github-actions]

The dependency autoupdater failed during builds-and-checks.

Run log: https://github.com/siarheidudko/firebase-admin-cli/actions/runs/35404610223

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

  npm run build
  npm test

Claude will leave a status comment on this PR when it finishes.
The Claude workflow re-dispatches PR-checks once it is done, so the
checks below reflect its pushed fixes.

[claude]

Status: no fix needed — no compatibility issue found.

• npm install --no-audit --no-fund: exit 0
• npm run build: exit 0 (no type/compat issues from the firebase-admin ^14.3.0 → ^14.4.0 bump on this branch)
• npm test: fails locally, but only because this sandbox has no SERVICE_ACCOUNT/serviceAccount.json — the CLI never prints its startup banner without valid Google credentials, so the shell test times out. This is expected per CLAUDE.md ("Without the secret the shell test fails") and unrelated to the dependency bump.

Root cause of the original run failure (35404610223): the autoupdater itself errored before/during builds-and-checks, not npm run build/npm test:

npm error command /usr/bin/git --no-replace-objects tag -m 1.2.31 v1.2.31
npm error fatal: tag 'v1.2.31' already exists

Confirmed refs/tags/v1.2.31 already exists on the remote (from a prior release), so npm version patch's internal git tag collided. This is an autoupdater/release-tooling tag collision, not a dependency-compatibility problem in the code — no product or type changes were required or made.

No commits pushed (working tree was already clean/green on build). Flagging the tag collision for the maintainer since it's outside the scope of a compatibility fix (per CLAUDE.md boundaries: not bumping version / not touching release pipeline).