scan-next: abort a dst plan on any error but a missing file
The executor ran each dst plan under catch_all, which swallowed
Borrower::Dead along with everything else, and treated every failed
dedupe the same way: a DATA_DIFFERS aborted the dst plan, while the
ref-slice build hid every error from a ref's extent data fetch.
Apply one rule everywhere a dst plan executes:
- ENOENT means the ref's file is gone. Skip that ref and keep going
(plan_ref_enoent).
- DATA_DIFFERS is not an error. The refs come from the commit root,
so they lag live data, and a live change is expected. Keep going
and let verification count the ref if it survives.
- Any other error, and a read-only dst, aborts that dst plan
(plan_dst_abort). Other dst plans in the same ExtentPlan still run.