IGNITE-21371 Add tx coordinator id to TX requests

[Cyrill]

https://issues.apache.org/jira/browse/IGNITE-21371

[sanpwc]

Do we really need txCoordinatorId in TxFinishReplicaRequest? Use-cases?

[Cyrill]

See PartitionListener.handleFinishTxCommand, line 351:

markFinished(txId, cmd.commit(), cmd.commitTimestamp(), cmd.txCoordinatorId());

[sanpwc]

I mean logically. Why do we need coordinatorId on finish request? From my point of view, we use coordinatorId retrieved from txnState local map in two cases only.

1. In order to check whether coordinator is dead and trigger the recovey, which definitely has no sense in case of finished transaction.
2. In order to decrement counter of an "in-flight" transactions that is used within index build procedure. In that case it's guaranteed that txnState local map will be populated with txCoordId prior to finish processing.

All in all, I believe that we may remove txCoordinatorId() from TxFinishReplicaRequest and update

    private void markFinished(UUID txId, boolean commit, @Nullable HybridTimestamp commitTimestamp) {
        txManager.updateTxMeta(txId, old -> new TxStateMeta(
                commit ? COMMITTED : ABORTED,
                old == null ? null : old.txCoordinatorId(),
...

[Cyrill]

Same applies to WriteIntentSwitch command handling

[sanpwc]

LGTM