Check HAVE_COPY_FILE_RANGE before calling copy_file_range
Fix a mistake in
ac8110155132 - write_reconstructed_file() called
copy_file_range() without properly checking HAVE_COPY_FILE_RANGE.
Reported by several macOS machines. Also reported by cfbot, but I missed
that issue before commit.