execution: commit the transaction before responding explain analyze results to the client (#38044)

[ti-chi-bot]

This is an automated cherry-pick of #38044

What problem does this PR solve?

Issue Number: close #37373

Problem Summary:
The explain analyze statement execution with DML executors may respond to the client before the transaction commit finishing.

What is changed and how it works?

Trigger the commit operation if the statement is an explain analyze statement with DML executors before returning the record set of itself.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
  • Sleep before the commit
  • Execute explain analyze
  • Check if it responses before the commit has finished
• No code

Side effects

Documentation

Release note

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

Fix the issue explain analyze with DML executors may respond to the client before the transaction commit has finished.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

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-chi-bot]

@ti-chi-bot: This cherry pick PR is for a release branch and has not yet been approved by release team.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick, it must first be approved by the collaborators.

AFTER it has been approved by collaborators, please ping the release team in a comment to request a cherry pick review.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[ti-chi-bot]

@ti-chi-bot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/build	4942239	link	true	/test build
idc-jenkins-ci-tidb/check_dev_2	4942239	link	true	/test check-dev2
idc-jenkins-ci-tidb/check_dev	4942239	link	true	/test check-dev
idc-jenkins-ci-tidb/unit-test	4942239	link	true	/test unit-test
idc-jenkins-ci-tidb/mysql-test	4942239	link	true	/test mysql-test

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[ti-chi-bot]

@ti-chi-bot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/build	4942239	link	true	/test build
idc-jenkins-ci-tidb/check_dev_2	4942239	link	true	/test check-dev2
idc-jenkins-ci-tidb/check_dev	4942239	link	true	/test check-dev
idc-jenkins-ci-tidb/unit-test	4942239	link	true	/test unit-test
idc-jenkins-ci-tidb/mysql-test	4942239	link	true	/test mysql-test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.