ci: use npm stage publish

[riderx]

What

• Switch production and PR beta publishes from npm publish to npm stage publish for @capacitor-plus/*.

Why

• npm no longer allows long-lived unattended publish tokens.

How

• CI stages core/cli/android/ios with the org NPM_TOKEN.
• Drop the pr-N dist-tag from beta comments.

Testing

• Workflow-only. Same stage flow as the Cap-go plugins.

Not Tested

• A live tagged release or /publish-beta on this repo.

Made with Cursor

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: eb25bc67-5361-44be-bc53-a26b77e475c0

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Beta npm build

Maintainers can publish one Capacitor Plus workspace package from this PR to npm for fast testing.

Comment /publish-beta <package> after the PR checks are green.

Examples:

/publish-beta core
/publish-beta cli
/publish-beta @capacitor-plus/core

If exactly one workspace package changed, /publish-beta without a package will use that package.

Packages:

• core (@capacitor-plus/core)
• cli (@capacitor-plus/cli)
• android (@capacitor-plus/android)
• ios (@capacitor-plus/ios)

The workflow will:

• publish a prerelease package on the beta tag
• add a pinned pr-108 dist-tag for the selected package
• update this comment with the install command

Security note: beta publish is only enabled for branches inside this repository.