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

[ti-srebot]

cherry-pick #38038 to release-6.3
You can switch your code base to this Pull Request by using git-extras:

# In tidb repo:
git pr https://github.com/pingcap/tidb/pull/38052

After apply modifications, you can push your change to this PR via:

git push git@github.com:ti-srebot/tidb.git pr/38052:release-6.3-5aab87679fde

---

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:

• crazycs520
• lcwangchao

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.

[ti-srebot]

/run-all-tests

[ti-srebot]

@tiancaiamao you're already a collaborator in bot's repo.

[tiancaiamao]

/run-unit-test

[wuhuizuo]

/run-unit-test

[tiancaiamao]

/merge

[ti-chi-bot]

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

Commit hash: 71e5453

[hawkingrei]

/run-build