* fix(monorepo): keep bumped manifests biome-clean

`lerna version` writes package.json with its own JSON formatter, which
disagrees with biome — it expands `"files": ["dist"]` across three lines and
`biome check` treats that as an error. Locally this never showed, because
husky's lint-staged silently reformatted the staged files as part of the
version commit. The release workflow's API commit bypasses git hooks, so the
4.0.3 bump landed on main unformatted and release-publish.yml failed at
`npm test` — after the release PR had already merged, leaving main red and
4.0.3 unpublished.

Reformats the 34 manifests the 4.0.3 bump left unformatted (whitespace only;
verified all 34 parse to semantically identical JSON and no version value
changed), and adds a "Format the bump" step to release-prepare.yml so future
bumps are formatted before the commit is authored.

Scoped to package.json/lerna.json deliberately: lock files are biome-clean
as npm writes them and are best left alone.

Refs: TASK-115

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* ci(monorepo): make the format step shell-agnostic

The step passed the manifest list as an unquoted expansion. That works on the
runner, where `run:` uses bash and word-splits it into separate arguments,
but not in zsh, which passes one newline-joined argument — biome then failed
with "File name too long" and reported that every path was ignored.

Pipe through xargs instead, so the same line behaves identically wherever it
is tested, and fail loudly if the bump produced no manifest changes.

Verified by simulating a 4.0.4 bump locally: biome exits 1 immediately after
`lerna version` (reproducing the 4.0.3 failure) and 0 once the step runs.

Refs: TASK-115

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>