*: Add a system table pipelined_dml_progress

[ekexium]

What problem does this PR solve?

Issue Number: ref #50215

Problem Summary:

TiCDC and TiFlash have not achieved full compatibility with Pipelined DML. When using pipelined DML, TiFlash replicas and changefeed need to be removed temporarily until all locks written by Pipelined DML are resolved, to avoid OOM risks.

This PR provides an approch for users to identify whether there are locks written by PDML unresolved yet.

What changed and how does it work?

Requires tikv/client-go#1610

1. Add a system table mysql.pipelined_dml_progress
2. Let pipelined DML update progress in the table
3. Let GC clear stale records in the table after resolving locks.

Example

insert into t2 select * from t;

select * from mysql.pipelined_dml_progress;

+--------------------+-----------------+----------------+------------------+---------------------+---------------------+
| start_ts           | involved_tables | status         | resolved_regions | create_time         | update_time         |
+--------------------+-----------------+----------------+------------------+---------------------+---------------------+
| 456614763033264130 | t2,t            | ResolvingLocks | 1                | 2025-03-13 14:24:48 | 2025-03-13 14:25:04 |
+--------------------+-----------------+----------------+------------------+---------------------+---------------------+

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

Add a system table `mysql.pipelined_dml_progress`

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from ekexium and additionally assign yudongusa for approval(Please ensuring that each of them provides their approval before proceeding). For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS
• pkg/session/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment