[Bug]:Duplicate entry error in optimistic mode

[ouyuanning]

Is there an existing issue for the same bug?

• I have checked the existing issues.

Branch Name

main, 2.0-dev

Commit ID

main, 2.0-dev

Other Environment Information

- Hardware parameters:
- OS type:
- Others:

Actual Behavior

mysql> create table t1(a int, b int, c int, primary key(a,b));
Query OK, 0 rows affected (0.02 sec)

mysql> insert into t1 select result,result,result from generate_series(200000) g;
Query OK, 200000 rows affected (0.33 sec)

mysql> update t1 set c =10 where a < 6000;
ERROR 1062 (HY000): Duplicate entry '3a15013a1501' for key '__mo_cpkey_col'

Expected Behavior

No response

Steps to Reproduce

1、use optimistic to start MO

//cn.toml
[cn.txn]
mode ="optimistic"

//tn.toml
[tn.txn]
mode ="optimistic"

2. run sql ：

select mo_ctl('cn', 'task', 'disable');
drop database if exists db1;
create database db1;
use db1;

create table t1(a int, b int, c int, primary key(a,b));
insert into t1 select result,result,result from generate_series(200000) g;
update t1 set c =10 where a < 6000; // error here

### Additional information

_No response_

[triump2020]

TN  dosen't receive deletes when  run upate statement : `update t1 set c =10 where a < 6000`

[triump2020]

进一步分析, 当运行update 语句时，是因为 txn commit 时，workspace 中的 delete 与insert entry 顺序颠倒，而导致了tn 先处理insert entry 的去重就会报dup.

workspace 中的 delete ,insert entry 顺序颠倒是因为 dumpbatch 函数导致的.

[triump2020]

wait for pr