lance-format#7373 made a DataReplacement conflict with any concurrent Update/Delete that
touched a target fragment. That is too conservative: a delete that only adds a
deletion vector leaves the positional column file aligned, and build_manifest
rebases the replacement onto the current fragment, preserving the deletion
vector.

A DataReplacement vs a concurrent Delete/Update now conflicts only when:
- the target fragment is removed outright -- returns a non-retryable
  IncompatibleTransaction so the caller can drop it and commit the rest;
- a row-rewriting (RewriteRows) update moves the matched rows out to new
  fragments the positional file does not cover; or
- the update rewrote one of the replaced fields in place (fields_modified).

Deletion-vector-only deletes/updates and non-overlapping column rewrites are
now allowed.

Update the DataReplacement compatibility table to match the refined conflict
resolver: full fragment removal by Delete/Update is now a non-retryable
conflict, Update is a retryable conflict only when it moves rows out of a
target fragment or rewrites one of the replaced fields, and a deletion-vector
-only Delete/Update is compatible.