Bump nedb-engine + client to v2.4.4, rename distro submodules (cryptoDB->crypto-database, nitroDB->aof-db), repoint distro CI

[Eth-Interchained]

Bump nedb-engine + nedb-engine-client to v2.4.4, rename distro submodules, repoint distro CI

Summary

Bumps the umbrella to v2.4.4, renames the two distro submodules to their new publish identities (cryptoDB → crypto-database, nitroDB → aof-db), repoints the nitro submodule URL to the renamed repo, and rewrites release-distros.yml so the v2.4.4 tag publishes both distros under their new names in parallel with the flagship engine.

Why this matters

This is the umbrella half of a coordinated three-repo rename. The distro repos already merged their renames (nitro-db/aof-DB @ b6df8a4, crypto-datab/cryptoDB @ d076d56). This PR pins the umbrella's submodule gitlinks to those merged commits, moves the folder paths to match the new names, and aligns the distro publish matrix so a single v2.4.4 tag fires release.yml (nedb-engine + client) and release-distros.yml (both distros) in parallel.

Engine impact

• nedb-engine bumped to 2.4.4 across all six version surfaces: package.json, pyproject.toml, python/nedb/__init__.py, rust/crates/nedb-py/pyproject.toml, rust/Cargo.toml [workspace.package], rust/nedb-v2/Cargo.toml.
• nedb-engine-client bumped to 2.4.4 in client/node/package.json and client/python/pyproject.toml. The client publishes via the existing release.yml client-pypi + client-npm jobs on the same tag.
• No engine code or behavior change — pure version bump.

Studio impact

None. Studio is a separate repo and is not touched by this PR.

Submodule changes

• .gitmodules: distributions/cryptoDB → distributions/crypto-database (crypto repo URL unchanged — crypto-datab/cryptoDB was not renamed on GitHub); distributions/nitroDB → distributions/aof-db with URL repointed nitro-db/nitroDB → nitro-db/aof-DB (that repo was renamed on GitHub).
• Submodule gitlinks pinned to the merged distro master commits:
  • distributions/aof-db → b6df8a4 (nitro-db/aof-DB, "rename!: nitroDB -> aof-db")
  • distributions/crypto-database → d076d56 (crypto-datab/cryptoDB, "rename!: cryptoDB -> crypto-database")
• Old submodule paths distributions/cryptoDB and distributions/nitroDB removed from the tree.

Distro CI (release-distros.yml)

• Matrix distro.name: cryptodb → crypto-database, nitrodb → aof-db across all five jobs (distro-node, distro-smoke, distro-publish-npm, distro-publish-crate, distro-pypi).
• Matrix distro.path: distributions/cryptoDB → distributions/crypto-database, distributions/nitroDB → distributions/aof-db.
• Inline matrix.distro == 'cryptodb' && ... ternaries updated to crypto-database / aof-db.
• cargo publish --package names now crypto-database / aof-db.
• Header note updated: submodules now track master and are pinned to the renamed commits; the distro/*-layer branch caveat is removed.
• PyPI note: crypto-database's own pyproject.toml keeps name = "cryptodb" on PyPI (the crypto-database name is taken by a third party); aof-db publishes as aof-db. The wheel name is read from each distro's pyproject, so no matrix change is needed for the PyPI job — documented inline.

Registry outcome on v2.4.4 tag

package	npm	PyPI	crates.io
nedb-engine	bump 2.4.3→2.4.4	bump 2.4.3→2.4.4	—
nedb-engine-client	bump 2.4.3→2.4.4	bump 2.4.3→2.4.4	—
crypto-database	NEW (free)	stays cryptodb 2.4.4	NEW (free)
aof-db	NEW (free)	NEW (free)	NEW (free)

Old cryptodb / nitrodb crates stay published on crates.io at 2.4.3 (cannot be deleted; yank later if desired).

Tests run

• Manifest validation: all 6 engine + 2 client version surfaces confirmed at 2.4.4; .gitmodules paths + nitro URL confirmed; workflow confirmed using crypto-database/aof-db with only the explanatory PyPI note retaining the old literal.
• The sandbox cannot link Rust or reach the npm registry, so CI is the real compiler and gate. The distro-smoke job runs each distro's test/smoke.mjs against the freshly-built addon and gates every publish job — a broken rename blocks publish rather than shipping a broken artifact. The engine release.yml runs its own tests/test_nedb.py before the PyPI publish.
• Per Mark's call: tag straight after merge (no pre-tag workflow_dispatch dry-run); CI is the gate.

Follow-up work

• Tag v2.4.4 on master after this PR merges; push via nedb-release --target github to fire both workflows.
• Pre-ship the umbrella universal wheel via nedb-release --target pypi alongside CI.
• Watch CI: https://github.com/Eth-Interchained/nedb/actions
• Consider yanking old cryptodb / nitrodb crates on crates.io once downstream consumers migrate.
• macOS-native distro wheels via Codemagic remain a documented follow-up (codemagic.yaml).

© INTERCHAINED LLC × Claude Sonnet 4.6