open_root and open_root_ino returned an empty Fd for every failure, so a
caller could not tell a deleted file from an I/O error, and the scan-next
executor skipped a dst ref that failed with EIO instead of aborting the
dst plan.
ENOENT stays a quiet empty Fd: deleted files and subvols are common, and
logging each one would flood the log. Every other INO_PATHS or openat
error now throws, and so does a validation failure (wrong inode, root, or
device). For a file with several paths, a failed path is remembered and
the rest are tried; the error is thrown only if none opens.