Find a way to aware accurate fragment id in operation of transaction

Recently, I have been implementing the diff feature #3979 .

By discussing with @jackye1995 , the suggestion is that it would be better to get the delta(changed) fragments' id from a transaction.

I find that it can not get the accurate fragment ID in the operation(e.g. Append) of a specific transaction. If an operation has multiple fragments, the IDs of the fragments always start from 0. Based on this, when we get a transaction of a version, we can not get the right fragment IDs. And it's hard to get the right FragmentReader to fetch data.

I know the current mechanism is that we assign the fragments' ID after writing the transaction file.

Just open this issue to discuss if we can make the transaction aware of the accurate fragment ID.

The issue points to transaction operations such as Append and the transaction-file write step, with diff feature #3979 as context. Start by tracing how fragment IDs are assigned after writing a transaction file; done means a version transaction can expose accurate changed-fragment IDs so the right FragmentReader can be selected.