fix: updates remove their own backups once verified and delete old updater backups (#201711)

* fix(update): remove a verified update's backups and old updater backups

An update's Doctor backups now record the update run that took them, and a
database rollback writes a receipt for the files it moves aside. Automatic
cleanup decides from the run outcome instead of the live database inode,
removes a verified update's own images and captures, deletes earlier
updater-owned sets, keeps the newest unverified set and anything a pending
recovery or unfinished run references, and reports what it freed and kept.

* fix(update): release already-current captures and rerun cleanup after verification

* fix(update): keep rollbacks and unverified images safe while cleaning up

Receipt writes never block a database rollback and keep the database
directory's mode. Non-restorable pre-migration images keep their existing
retention. A changed newest set no longer releases older sets, the ledger
keeps the cleanup report on every finished run, and a failed run's sealed
capture is released by a later verified update.

* fix(update): release update backups per database, never per run

An older backup of a database is released only by a verified update after
it or by an intact backup of the same database from a later run; a moved-aside
family counts as intact only when every recorded member is present. Receipt
reads count against the status scan budget, a cleanup rerun replaces the
recorded report, sizes are reported as logical bytes and the suggested
removal path is shell-quoted.

* fix(update): re-prove successors, keep live-database checks, scan configured agent dirs

A newer Doctor backup releases an older one only after its recorded content
is re-verified, and moved-aside families never stand in for older backups.
Released backups still require a present, unaliased live database. Receipts
alone load run history, configured agent directories are scanned, a volume
renumbered by a reboot keeps its receipt valid, and a settled rerun clears an
earlier cleanup warning instead of restating it.

* fix(update): keep copies while their live database is missing and report cleanup in text output

Moved-aside families now need a present live database before removal, as
Doctor backups do. Bounded status and read-only Doctor never hash a backup.
The plain-text update report prints the cleanup summary, a warning-only
attempt replaces the recorded summary, and the suggested removal path uses
the CLI quoting helpers for the platform.

* fix(update): require full successor images, running-run tags, and a live database for moved-aside copies

* test: record the test-line allocation for the round-four regressions

* chore(pr): add the update run reader to the wrapper inventory