[spark] Support V2 UPDATE for data evolution tables

[kerwin-zk]

Purpose

Support V2 UPDATE for data evolution tables.

Tests

CI

[JingsongLi]

How to support delete row ids? cc @leaves12138

[kerwin-zk]

How to support delete row ids? cc @leaves12138

@JingsongLi Deleted row ids are simply retired — they become holes in the row-id space. Surviving rows always keep their original row ids, and no physical _ROW_ID column is ever written, so row ids stay derived from firstRowId + position, exactly like the files produced by DataEvolutionDeleteRewriter in #8182

[JingsongLi]

+1 from my side, no blocking issues found

[JingsongLi]

How to support delete row ids? cc @leaves12138

@JingsongLi Deleted row ids are simply retired — they become holes in the row-id space. Surviving rows always keep their original row ids, and no physical _ROW_ID column is ever written, so row ids stay derived from firstRowId + position, exactly like the files produced by DataEvolutionDeleteRewriter in #8182

@kerwin-zk It's too troublesome to maintain the index after deletion. Maybe the correct solution is deletion-vector. Can you just support update in this PR?

[JingsongLi]

This path skips the IOManager setup that the normal V2 writer does before creating append writers. If a data-evolution table has write-buffer-for-append=true (with the default spillable buffer), AppendOnlyWriter builds an ExternalBuffer with a null IOManager; once the buffer spills, it will fail at ioManager.createChannel(). Please pass an IOManager into this TableWriteImpl (and close it with the writer), or otherwise disable the buffered append path here.