fix(firestore-counter): repair package-lock for builder npm

[cabljac]

Problem

CI on next fails uploading firestore-counter@0.2.17-rc.0:

npm ERR! `npm ci` can only install packages when your package.json and package-lock.json ... are in sync
npm ERR! Missing: ts-node@10.9.2 from lock file

Root cause

The extensions builder falls back to npm 9 (its nvm install 22 fails: "version v22 is not yet installed"). npm 9's npm ci auto-resolves jest-config's optional peer ts-node: >=9.0.0 to ts-node@10.9.2 and demands that subtree in the lock. The lock (last regenerated with a newer npm) only carried the direct ts-node@7.0.1 and lacked the 10.9.2 tree.

Reproduced locally: npm@9 ci fails with the identical error; npm@11 ci passes, which is why it slipped through.

Fix

• package.json: remove unused ts-node@^7.0.1. The ts-jest preset does not use it; sibling extensions (firestore-send-email, storage-resize-images) run the same preset with no ts-node.
• package-lock.json: surgically regenerated from the committed lock (npm@9 install --package-lock-only). Only the ts-node subtree changed; @types/node@22.19.17 and all other pins are untouched. A from-scratch regen was avoided because it floats @types/node and breaks tsc@4.9.

Validation

• npm ci exit 0 under both npm 9 (builder) and npm 11
• npm ci -> build (tsc) exit 0
• unit tests: 14 pass (only controller.emulator.test.ts fails, which needs a running Firestore emulator)

[gemini-code-assist]

Code Review

This pull request removes ts-node from the development dependencies in package.json and updates the package-lock.json file accordingly. There are no review comments to assess, and I have no additional feedback to provide.