fix(release): install (not ci) on the FreeBSD legs

FreeBSD's pkg ships a newer npm than the GitHub-hosted node22 runners, and that
newer npm fails `npm ci` on the @retrigger/core-* platform optionalDependencies:
they have no resolved nodes in the lock because they are unpublished (404) until
this release publishes them, and strict npm counts that as a package.json vs
package-lock.json desync ("Missing ... from lock file", EUSAGE). The exact
committed lock passes `npm ci` on npm 11.0.0 in clean isolation, so the lock is
not the defect -- the npm version is. Use `npm install` on the two FreeBSD build
legs, which reconciles rather than strictly validating; the hosted runners keep
`npm ci`. verify-published-freebsd already installs from the registry.

Author: GriffinCanCode

.github/workflows/ci.yml

@@ -175,7 +175,12 @@ jobs:
             set -eu
             . "$HOME/.cargo/env"
             cd src/bindings/nodejs
-            npm ci --no-audit --no-fund
+            # `npm install`, not `npm ci`: FreeBSD's pkg ships a newer, stricter npm
+            # that fails `npm ci` because the unpublished @retrigger/core-* platform
+            # optionalDependencies have no resolved nodes in the lock (they 404 until
+            # the release publishes them). install reconciles instead of strictly
+            # validating, so the leg is not blocked by a chicken-and-egg.
+            npm install --no-audit --no-fund
             npm run build
             npm test
             npm run test:pack

.github/workflows/release.yml

@@ -275,7 +275,12 @@ jobs:
             set -eu
             . "$HOME/.cargo/env"
             cd "$NODE_DIR"
-            npm ci --no-audit --no-fund
+            # `npm install`, not `npm ci`: FreeBSD's pkg ships a newer, stricter npm
+            # that fails `npm ci` because the unpublished @retrigger/core-* platform
+            # optionalDependencies have no resolved nodes in the lock (they 404 until
+            # this very release publishes them). install reconciles instead of
+            # strictly validating, so the build leg is not blocked by a chicken-and-egg.
+            npm install --no-audit --no-fund
             npm run build
             node scripts/verify-artifact.js
             test -f retrigger-nodejs-bindings.freebsd-x64.node