fix: Reorder npm upgrade to prevent lock file sync errors (#143)

This change ensures npm is upgraded AFTER installing dependencies rather
than before. Upgrading npm before running npm ci causes package-lock.json
sync errors that prevent successful dependency installation.

The issue occurs because different npm versions may use different lock
file formats. When npm is upgraded before dependencies are installed, the
subsequent npm ci command detects a format mismatch and fails with:
"npm ci can only install packages when your package.json and
package-lock.json or npm-shrinkwrap.json are in sync."

Testing confirmed this order resolves the issue:
1. Install dependencies with current npm version (works)
2. Upgrade npm to latest (maintains lock file compatibility)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude <[email protected]>

Author: rfgamaral

.github/workflows/core-deploy.yml

@@ -55,12 +55,15 @@ jobs:
                   registry-url: https://registry.npmjs.org/
                   scope: '@doist'
 
-            - name: Ensure npm 11.5.1 or later is installed
-              run: npm install -g npm@latest
-
             - name: Install dependencies
               run: npm run bootstrap-ci:common
 
+            # npm must be upgraded AFTER installing dependencies to avoid package-lock.json
+            # sync errors. Upgrading npm before running npm ci can cause lock file format
+            # mismatches that prevent successful dependency installation.
+            - name: Ensure npm 11.5.1 or later is installed
+              run: npm install -g npm@latest
+
             - name: Publish package
               working-directory: ./packages/ui-extensions-core
               run: npm publish --provenance --access public