fix: resolve npm --no-workspaces and --workspace conflict in bump-version CI (#37)

Run npm install --package-lock-only in a temp directory outside the
monorepo so npm cannot detect workspace membership or traverse the root
.npmrc (workspaces=false). This avoids the conflict between the implicit
--no-workspaces flag set by root .npmrc and the --workspace flag that
npm v9/v10 auto-sets when the CWD is inside a workspace member directory.

Copies the existing package-lock.json into the temp dir first so npm
makes incremental changes rather than regenerating from scratch.

Author: ajainvivek

.github/workflows/bump-version.yml

@@ -76,8 +76,15 @@ jobs:
           node-version: "20"
 
       - name: Update client package-lock.json
-        working-directory: apps/reasondb-client
-        run: npm install --package-lock-only --ignore-scripts
+        run: |
+          PKGDIR="${RUNNER_TEMP}/npm-lockonly"
+          mkdir -p "$PKGDIR"
+          cp apps/reasondb-client/package.json "$PKGDIR/"
+          if [ -f apps/reasondb-client/package-lock.json ]; then
+            cp apps/reasondb-client/package-lock.json "$PKGDIR/"
+          fi
+          npm install --package-lock-only --ignore-scripts --prefix "$PKGDIR"
+          cp "$PKGDIR/package-lock.json" apps/reasondb-client/package-lock.json
 
       - name: Install Rust stable (for Cargo.lock update)
         uses: dtolnay/rust-toolchain@stable