ci: use npm ci for reproducible installs across all jobs

All five CI jobs ran 'npm install', which resolves caret-ranges against the live npm registry and ignores package-lock.json. This caused dependency drift between local runs and CI — most recently suspected as a contributor to the SaaS 8.7 hard-fail in Worker-Failure-Retries.spec.ts (passes locally with the locked grpc-js, fails in CI with whatever the resolver picked).

Switching to 'npm ci' makes CI installs deterministic against package-lock.json. If we still see the 8.7 failure after this lands, we can rule dependency drift out and look elsewhere (Node 22 vs local Node, GHA runner network/TLS, etc.).

Author: jwulf

.github/workflows/ci.yml

@@ -28,7 +28,7 @@ jobs:
           node-version: "22"
 
       - name: Install dependencies
-        run: npm install
+        run: npm ci
 
       - name: Build and Smoke Test
         run: npm run test:smoketest
@@ -51,7 +51,7 @@ jobs:
           node-version: "22"
 
       - name: Install dependencies
-        run: npm install
+        run: npm ci
 
       # Workaround for https://github.com/actions/runner-images/issues/2821
       - name: Remove mono blocking 8084 port
@@ -100,7 +100,7 @@ jobs:
           node-version: "22"
 
       - name: Install dependencies
-        run: npm install
+        run: npm ci
 
       # Workaround for https://github.com/actions/runner-images/issues/2821
       - name: Remove mono blocking 8084 port
@@ -153,7 +153,7 @@ jobs:
           node-version: "22"
 
       - name: Install dependencies
-        run: npm install
+        run: npm ci
 
       - name: Run Integration Tests
         run: |
@@ -190,7 +190,7 @@ jobs:
           node-version: "22"
 
       - name: Install dependencies
-        run: npm install
+        run: npm ci
 
       - name: Run Integration Tests
         run: |