chore(release): bump workspace version to 0.1.13

[robinnsc]

What

Bumps the workspace version 0.1.12 → 0.1.13 across every version-carrying
surface: root Cargo.toml, the twelve workspace entries in Cargo.lock, all
three license-notices files (postgres, mongodb, dev), the npm launcher
manifest (version + five platform pins), and the docs example-output strings.
No source or dependency change.

Why

Opens the 0.1.13 release line for the six commits merged since v0.1.12:
stream sequence-number normalization (#353), HLC instance-id wiring (#352),
chunked Query/Scan page reads (#354), index cursor direction fixes (#362),
PostgreSQL COLLATE "C" key columns (#361), and the settle-window
recalibration (#363).

Testing done

• cargo check --workspace --all-targets --locked — clean.
• All three notices --checks pass with the pinned cargo-about 0.9.0.
• Repo-wide grep: no remaining 0.1.12 references outside changelogs and
  notices.
• Cargo.lock diff: only workspace extenddb* crates move; no third-party
  entries changed.

Checklist

• All tests pass (cargo test --workspace) — not re-run: no source or dependency change
• Code is formatted / clippy — not applicable, no Rust source changed
• I have added or updated tests for new functionality — not applicable
• I have updated documentation if behavior changed — docs version strings updated
• Breaking changes are noted below (if any)

ADR / RFC: n/a — version metadata only.

Breaking changes

None.

---

By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache License 2.0 and I agree to the Developer Certificate of
Origin (DCO). See CONTRIBUTING.md for details.

[jcshepherd]

LGTM. Is there a run-book or such for doing these bumps, or is it a matter of grepping and tribal knowledge?