feat: add crates.io publishing and synchronize versions across all manifests

[Copilot]

PluresDB now publishes to crates.io alongside existing npm, JSR, Docker Hub, winget, and GitHub Releases channels. All version files are synchronized at 1.3.8.

Changes

Release Automation

• Added publish-crates job to release workflow publishing in dependency order: pluresdb-core → pluresdb-storage → pluresdb-sync → pluresdb-cli
• CI now syncs deno.json version alongside package.json and Cargo.toml during automated bumps
• Added 30s delays between crate publishes to ensure registry availability

Documentation

• README: Added crates.io badge and Cargo installation instructions
• RELEASE_PROCESS: Documented crates.io workflow and CARGO_REGISTRY_TOKEN secret
• ROADMAP: Updated to January 2026 status reflecting all completed phases
• CHANGELOG: Added unreleased section with current improvements

Build

• Added Node types to tsconfig.json to fix compilation of Node.js-specific entry points

Installation

# Rust developers can now use:
cargo add pluresdb-core pluresdb-storage pluresdb-sync

# Alongside existing channels:
npm install pluresdb                    # Node.js
deno add @plures/pluresdb              # Deno/JSR
docker pull pluresdb/pluresdb:latest   # Docker
winget install pluresdb.pluresdb       # Windows

Release Flow

On merge to main with feat: commit:

1. CI bumps version (1.3.8 → 1.4.0)
2. Updates all manifests: package.json, Cargo.toml, deno.json
3. Creates tag v1.4.0
4. Publishes to npm, crates.io, JSR, Docker Hub, GitHub Releases simultaneously

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Bump all versions, tag, release, and publish</issue_title>
<issue_description>Based on the latest improvements to the code base, we should bump all versions, ensuring they are in sync.
It's also time for us to publish on crates.io in addition to NPM, GitHub packages, JSR, and making binaries available on GitHub releases. Update the workflow to implement the required changes, and update readme.md, changelog.md, and any other documentation files to align with the latest changes and advancements we have made to the project and road-map. </issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Bump all versions, tag, release, and publish #33

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.