ddl: fix a bug that 'flashback table' does not handle mysql.gc_delete_range correctly

[tiancaiamao]

What problem does this PR solve?

Issue Number: close #37386

Problem Summary:

What is changed and how it works?

@crazycs520 regard the element_id of mysql.gc_delete_range as table ID mistakenly...
So the constructed SQL from deleting the gc_delete_range record is wrong.

element_id is not table id, it's just an ID to distinguish multiple records within a job.

Check List

Tests

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

unistore doesn't implement the flashback table utilities, so I can't write the unit test.
I verified that #37386 is solved after this change.
And also,

create table pt (id int) partition by hash(id) partitions 5;
drop table pt;
flashback table pt;

create table a (id int);
create table b (id int);
drop table a,b;
flashback table b;

truncate table b;
flashback table b;

Check the gc_delete_range is correct in each step.

• No code

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.

Fix a bug that 'flashback table' does not handle `mysql.gc_delete_range` correctly, this bug make the 'flashback table' feature almost unavailable.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• tangenta
• wjhuang2016

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[xiongjiwei]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 554507f

[crazycs520]

In the code version of #13109, the element_id of mysql.gc_delete_range really is use to store the table_ID or index_id, so the issue #37386 won't exist in the old version.

[tiancaiamao]

After discuss with @crazycs520 , it's not him who misunderstand the element id and table id
At that time, the semantic is indeed table id...

Later, #33726 try to fix another bug, and change the element id, and then, introduce this bug.

[tiancaiamao]

/merge

[tiancaiamao]

/run-unit-test

[tiancaiamao]

/run-unit-test

[ti-srebot]

cherry pick to release-6.1 in PR #38050

[tiancaiamao]

/run-cherry-picker

[ti-srebot]

cherry pick to release-6.3 in PR #38052

[sre-bot]

TiDB MergeCI notify

🔴 Bad News! [3] CI still failing after this pr merged.
These failed integration tests don't seem to be introduced by the current PR.

CI Name	Result	Duration	Compare with Parent commit
idc-jenkins-ci-tidb/common-test	🔴 failed 1, success 10, total 11	53 min	Existing failure
idc-jenkins-ci-tidb/integration-ddl-test	🔴 failed 1, success 5, total 6	23 min	Existing failure
idc-jenkins-ci-tidb/tics-test	🔴 failed 1, success 0, total 1	6 min 13 sec	Existing failure
idc-jenkins-ci/integration-cdc-test	🟢 all 37 tests passed	26 min	Existing passed
idc-jenkins-ci-tidb/integration-common-test	🟢 all 17 tests passed	10 min	Existing passed
idc-jenkins-ci-tidb/sqllogic-test-2	🟢 all 28 tests passed	4 min 19 sec	Existing passed
idc-jenkins-ci-tidb/sqllogic-test-1	🟢 all 26 tests passed	3 min 57 sec	Existing passed
idc-jenkins-ci-tidb/mybatis-test	🟢 all 1 tests passed	3 min 11 sec	Existing passed
idc-jenkins-ci-tidb/integration-compatibility-test	🟢 all 1 tests passed	2 min 58 sec	Existing passed
idc-jenkins-ci-tidb/plugin-test	🟢 build success, plugin test success	4min	Existing passed