chore(release): publish npm and PyPI alongside Rust releases

[shps951023]

Summary

Release Node.js and Python together with the Rust core, and align both bindings on version 0.7.0.

Changes

• Align minipdf-node (package.json, package-lock.json, Cargo.toml) with the Rust core at 0.7.0.
• Add rust-ecosystem-release.yml: a rust-vX.Y.Z release validates that the Rust, npm, and Python package versions match the tag, then dispatches npm-publish.yml (staged) and pypi-publish.yml with that version.
• Switch the PyPI wheel matrix macOS Intel runner from macos-13 to macos-15-intel (matching the npm workflow) to avoid long Intel macOS queues.
• Document the version-follow convention in FEATURE_PARITY.md.

Summary by CodeRabbit

• New Features

  • Added coordinated release support for the Rust, Node.js, and Python packages, helping matching versions publish together.
  • Added guidance for keeping package versions synchronized across ecosystems.

• Improvements

  • Updated macOS binary builds to support macOS 14 and Intel-based macOS 15 environments.
  • Updated the Node.js package version to 0.7.0.

[coderabbitai]

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 42d7ad06-1734-4423-af13-7b2ff0d0f174

📥 Commits

Reviewing files that changed from the base of the PR and between 56d6c98 and 380b6a9.

⛔ Files ignored due to path filters (2)

• minipdf-node/Cargo.lock is excluded by !**/*.lock
• minipdf-node/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (5)

• .github/workflows/pypi-publish.yml
• .github/workflows/rust-ecosystem-release.yml
• FEATURE_PARITY.md
• minipdf-node/Cargo.toml
• minipdf-node/package.json

 _____________________________________
< CORS error? I'll cross that bridge. >
 -------------------------------------
  \
   \   (\__/)
       (•ㅅ•)
       / 　 づ

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

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