Update links-notation to the latest release (0.16.1->0.22.0) and enforce dependency freshness in CI #104

Summary

Every dependency of this repository should be at its latest release (the maintainers' standing requirement, applied first in link-assistant/formal-ai#1169). The latest published link-cli (0.2.11) and rust/Cargo.toml on main (checked 2026-09-29) declare dependencies whose latest release is outside the declared range:

Consumers such as link-assistant/formal-ai compile a second copy of these crates next to the current ones, and cannot move to current versions of shared types.

Requirements

1. R1: update every dependency in the table to its latest release and adapt the code to the new APIs (list each breaking change handled in the pull request description).
2. R2: run cargo update so the lockfile has no semver-compatible update pending (cargo update --dry-run prints no Updating lines).
3. R3: add a CI job that fails when a direct dependency is behind its latest release, unless the manifest line carries a comment with an open issue URL explaining the blocker. A ready-made form: cargo install cargo-outdated --locked && cargo outdated --root-deps-only --exit-code 1 (for JavaScript packages in this repository: npm outdated exits 1 when anything is outdated).
4. R4: publish a release containing the updates (crates.io and npm where applicable).

How to test

cargo outdated --root-deps-only --exit-code 1 exits 0; cargo tree -d in a fresh crate that depends on this release and on the latest versions of the crates in the table shows no duplicates for them.