exeuctor: fix coprocessor goroutine leak for IndexMerge (#41610)

[ti-chi-bot]

This is an automated cherry-pick of #41610

What problem does this PR solve?

Issue Number: close #41605

Problem Summary: As issue said, for partialIndexWorker and partialTableWorker of IndexMerge, we may failed to call SelectResult.Close when got panic(oom) in IndexMerge.fetchHandles(). Therefore goroutines in coprocessor that tries to send copResp will stuck, because receiver already panic and copIterator.finishCh is never closed.

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.

exeuctor: fix coprocessor goroutine leak for IndexMerge

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• XuHuaiyu
• guo-shaoge

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.

[guo-shaoge]

/merge

[ti-chi-bot]

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

Commit hash: e08620d

[guo-shaoge]

/test check_dev

[ti-chi-bot]

@guo-shaoge: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test build
• /test check-dev
• /test check-dev2
• /test mysql-test
• /test unit-test

Use /test all to run all jobs.

In response to this:

/test check_dev

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.

[guo-shaoge]

/test check-dev

[guo-shaoge]

/test check-dev

[guo-shaoge]

/merge

[guo-shaoge]

/retest

[guo-shaoge]

/retest

[guo-shaoge]

--- FAIL: TestStalenessTransactionSchemaVer (0.57s)
stale_txn_test.go:545:
Error Trace: stale_txn_test.go:545
Error: Not equal:
expected: 35
actual : 34
Test: TestStalenessTransactionSchemaVer
FAIL