v2.2.2

fix(ci): stop gating the release on the GHCR `latest` tag

`configure` failed with `Failed to find package 'open-data-capture-api'
with tag 'latest'`, blocking every release since v2.2.1.

`build` pushes `latest` and the bare version onto one manifest, so
deleting the bad v2.2.0/v2.2.1 container versions deleted the only
manifest carrying `latest`, and `release.cjs` threw on its absence.

That lookup never gated anything: its regex required a leading `v` while
the images are tagged bare, so `should_release` has always been `'true'`.
Its only live behaviour was this failure. Read the version from the root
`package.json` and release unconditionally, which is what already
happened, minus a dependency on registry state that a deleted release can
wipe out.

Also drop `.github/scripts/lib.js` — unreferenced, ESM in a CommonJS
directory, and a copy of the same lookup that queries a hardcoded
`open-data-capture-api` for all three packages.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>