ci(deserializer): update npm publishing workflow to use new tag input

Author: TartanLeGrand

.github/workflows/publish-npm-deserializer.yml

@@ -13,27 +13,16 @@ on:
         default: nightly
 
 jobs:
-  set-env:
-    runs-on: ubuntu-latest
-    outputs:
-      resolved-environment: ${{ steps.setenv.outputs.env }}
-    steps:
-      - id: setenv
-        run: |
-          if [ "${{ github.event.inputs.tag }}" = "latest" ]; then
-            echo "env=production" >> $GITHUB_OUTPUT
-          else
-            echo "env=staging" >> $GITHUB_OUTPUT
-          fi
-
   publish-npm:
     needs: set-env
-    uses: iExecBlockchainComputing/github-actions-workflows/.github/workflows/publish-npm.yml@publish-npm-v1.3.0
+    uses: iExecBlockchainComputing/github-actions-workflows/.github/workflows/publish-npm.yml@feat/publish-npm
     with:
       scope: '@iexec/deserializer'
       registry: 'https://registry.npmjs.org'
       node-version: '18'
-      environment: ${{ needs.set-env.outputs.resolved-environment }}
+      tag: ${{ github.event.inputs.tag }}
+      install-command: 'npm ci && npm run test:prepare'
+      environment: ${{ needs.set-env.outputs.resolved-environment }} # For secrets env
       working-directory: "packages/dataprotector-deserializer"
     secrets:
       npm-token: ${{ secrets.NPM_TOKEN }}