executor: replace Call with `WithRecovery in the close of hash join v1

[xzhangxian1008]

What problem does this PR solve?

Issue Number: close #60926

Problem Summary:

What changed and how does it work?

We replace Call with WithRecovery 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

[tiprow]

Hi @xzhangxian1008. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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.

[codecov]

Codecov Report

Attention: Patch coverage is 75.00000% with 3 lines in your changes missing coverage. Please review.

Project coverage is 72.9810%. Comparing base (1040e03) to head (b614712).
Report is 142 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #61868        +/-   ##
================================================
- Coverage   73.0288%   72.9810%   -0.0479%     
================================================
  Files          1730       1753        +23     
  Lines        481656     508376     +26720     
================================================
+ Hits         351748     371018     +19270     
- Misses       108355     115338      +6983     
- Partials      21553      22020       +467     

Flag	Coverage Δ
integration	42.5275% <50.0000%> (?)
unit	72.2274% <75.0000%> (-0.0497%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.7804% <ø> (ø)
parser	∅ <ø> (∅)
br	44.7585% <ø> (-1.8066%)	⬇️

🚀 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.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.1: #62341.
But this PR has conflicts, please resolve them!

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #62342.
But this PR has conflicts, please resolve them!

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #62343.
But this PR has conflicts, please resolve them!

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #62345.
But this PR has conflicts, please resolve them!

[xzhangxian1008]

/cherrypick release-6.5-20250805-v6.5.12

[ti-chi-bot]

@xzhangxian1008: new pull request created to branch release-6.5-20250805-v6.5.12: #62827.
But this PR has conflicts, please resolve them!

In response to this:

/cherrypick release-6.5-20250805-v6.5.12

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 ti-community-infra/tichi repository.