refactor(workflow): simplify NPM publish for automation tokens only

[hectoruch]

Simplify auto-publish workflow to use NPM automation tokens exclusively

• Remove OTP support and conditional logic for 2FA
• Streamline publish commands for automation token usage
• Update error messages with automation token specific guidance
• Clarify that workflow expects NPM_TOKEN to be an automation token

This change assumes the repository uses NPM automation tokens which bypass 2FA and don't require OTP codes, making the publishing process fully automated.

[github-actions]

❌ Auto-publish Failed

The automatic publication process failed. Please check the workflow logs for details.

🔧 Common Solutions

• NPM Token: Verify NPM_TOKEN is valid and has publish permissions
• Automation Token: Ensure you're using an NPM automation token (bypasses 2FA)
• Token Permissions: Check that the token has publish permissions for this package
• Version Conflict: Check if version already exists in NPM
• Build Issues: Ensure all tests pass locally and build completes successfully

🔐 NPM Token Requirements

1. Type: Must be an "Automation" token from npmjs.com
2. Scope: Should have access to publish the package
3. Permissions: Must have publish permissions
4. Secret: Should be stored as NPM_TOKEN in repository secrets

📞 Next Steps

1. Verify NPM_TOKEN is an automation token with correct permissions
2. Check the error logs for specific authentication issues
3. Create a new PR with the same changes
4. Or use manual publish workflow if urgent