fix: use proper @macayaven namespace for GitHub Packages

- Call update-npm-for-fork.sh for GitHub Packages registry
- Call prepare-fork-npm.sh for public npm registry
- Ensure packages use @macayaven namespace when publishing to GitHub Packages
- Maintain proper package naming for each registry type

This ensures GitHub Packages use scoped names (@macayaven/kubernetes-mcp-server)
while public npm uses descriptive names (kubernetes-mcp-server-openshift-ai).

Author: macayaven

.github/workflows/publish-npm.yml

@@ -74,7 +74,16 @@ jobs:
     - name: Prepare packages
       run: |
         chmod +x ./prepare-fork-npm.sh
-        ./prepare-fork-npm.sh "${{ github.event.inputs.suffix }}"
+        chmod +x ./update-npm-for-fork.sh
+        
+        # Use different preparation based on registry type
+        if [ "${{ github.event.inputs.registry }}" = "github-packages" ]; then
+          echo "🔧 Preparing packages for GitHub Packages with @macayaven namespace..."
+          ./update-npm-for-fork.sh macayaven
+        else
+          echo "🔧 Preparing packages for public npm with suffix ${{ github.event.inputs.suffix }}..."
+          ./prepare-fork-npm.sh "${{ github.event.inputs.suffix }}"
+        fi
 
     - name: Update versions
       run: |