This is an automated cherry-pick of #38738

What problem does this PR solve?

Issue Number: close #38669, #24427

Problem Summary:

Root cause of the issue is that in HandleDDLJobTable it will

1. start a new transaction
2. call runReorgJob for reorganization work, which can update mysql.tidb_ddl_reorg table in a new transaction, for 'savepoints' in case of crash, so it can continue instead of having to restart from the beginning.
3. when runReorgJob returns it will delete the job from mysql.tidb_ddl_reorg and commit the transaction started in 1) and if 2) did update the same table, this is where the commit conflict will occur, resulting in updates to reorg_meta will not be committed and the warnings and other updates will be lost.

What is changed and how it works?

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• 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.

None