fix: Correct NPM publishing command in workflows

- Fixed npm publish command to use package.json instead of package-npm.json
- Updated both npm-publish-only.yml and publish-all.yml workflows
- Now properly replaces package.json with NPM version before publishing
- This resolves the 404 error when trying to publish package-npm.json as a package name

The workflow now:
1. Creates a copy of package.json with unscoped name
2. Replaces the original package.json with NPM version
3. Publishes using standard npm publish command

Author: syrex1013

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

@@ -54,9 +54,11 @@ jobs:
           delete pkg.publishConfig;
           require('fs').writeFileSync('package-npm.json', JSON.stringify(pkg, null, 2));
         "
+        # Replace the original package.json with the NPM version
+        mv package-npm.json package.json
       
     - name: Publish to NPM
-      run: npm publish package-npm.json
+      run: npm publish
       env:
         NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 

.github/workflows/publish-all.yml

@@ -56,9 +56,11 @@ jobs:
           delete pkg.publishConfig;
           require('fs').writeFileSync('package-npm.json', JSON.stringify(pkg, null, 2));
         "
+        # Replace the original package.json with the NPM version
+        mv package-npm.json package.json
       
     - name: Publish to NPM
-      run: npm publish --package-lock=false
+      run: npm publish
       env:
         NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}