Fix appended file reuse
Build appended file targets per verification
Appended files were stored as Targets, and a binary one holds a live stream. The
engine disposes the stream of every target it writes, so a second Verify with
the same settings instance failed with ObjectDisposedException, even though the
caller had handed over re-readable bytes or a file path. Settings are reused
routinely, since SettingsTask copies them per Verify call.
They are now stored as factories and built once per verification:
AppendContentAsFile(byte[]) opens a fresh MemoryStream over the same array, and
AppendFile(string) opens the file per verification instead of holding a handle
from the moment it was appended. Existence is still checked eagerly, so a
missing path is still reported where it was passed.
AppendFile(Stream) is unchanged and still single use: the stream is owned by the
caller and cannot be replayed. That is now documented on the overload.