executor: replace Call with CallWithRecover in the close of hash join v1 (#61868)

[ti-chi-bot]

This is an automated cherry-pick of #61868

What problem does this PR solve?

Issue Number: close #60926

Problem Summary:

What changed and how does it work?

We introduce a new function CallWithRecover to recover the panic in the close of hash join v1

Check List

Tests

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

  • I checked and no code files have been changed.

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 the issue that the panic in the close of hash join v1 is not recovered

[ti-chi-bot]

@xzhangxian1008 This PR has conflicts, I have hold it.
Please resolve them or ask others to resolve them, then comment /unhold to remove the hold label.

[codecov]

Codecov Report

Attention: Patch coverage is 50.00000% with 5 lines in your changes missing coverage. Please review.

Please upload report for BASE (release-6.5@a28adfd). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-6.5     #62345   +/-   ##
================================================
  Coverage               ?   73.6379%           
================================================
  Files                  ?       1098           
  Lines                  ?     353698           
  Branches               ?          0           
================================================
  Hits                   ?     260456           
  Misses                 ?      76499           
  Partials               ?      16743           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[xzhangxian1008]

/retest

[ti-chi-bot]

@xzhangxian1008: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to this:

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-sigs/prow repository.

[windtalker]

lgtm

[xzhangxian1008]

/unhold

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: guo-shaoge, windtalker, xzhangxian1008

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [guo-shaoge,windtalker]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2025-07-16 02:08:31.514992295 +0000 UTC m=+2656764.238171308: ☑️ agreed by windtalker.
• 2025-07-16 06:08:49.982945535 +0000 UTC m=+2671182.706124777: ☑️ agreed by guo-shaoge.