stmt: clean rowContainer if the execution paniced

[YangKeao]

What problem does this PR solve?

Issue Number: close #59963, close #59976

Problem Summary:

1. The row container will not be closed if the exclusion panic.
2. The results and cursor will not be reset if there is an error in cc.flush.

What changed and how does it work?

1. Set the row container of stmt right after creating it. Therefore, it can be closed after closing the connection.

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.

Release note

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

None

[YangKeao]

/check-issue-triage-complete

[Defined2014]

Please update bazel

[Defined2014]

The comments it a littile dup with L390.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.4891%. Comparing base (ae830dc) to head (07ae424).
Report is 6 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #59985        +/-   ##
================================================
+ Coverage   73.0798%   73.4891%   +0.4092%     
================================================
  Files          1702       1702                
  Lines        470061     470483       +422     
================================================
+ Hits         343520     345754      +2234     
+ Misses       105368     103534      -1834     
- Partials      21173      21195        +22     

Flag	Coverage Δ
integration	42.7272% <0.0000%> (?)
unit	72.2850% <100.0000%> (-0.0054%)	⬇️

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

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	47.2088% <ø> (-0.0028%)	⬇️

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

[YangKeao]

/retest

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Defined2014, lcwangchao

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 [Defined2014,lcwangchao]

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-03-10 08:14:59.308045079 +0000 UTC m=+170854.913573998: ☑️ agreed by Defined2014.
• 2025-03-10 09:31:32.428070562 +0000 UTC m=+175448.033599490: ☑️ agreed by lcwangchao.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #59999.
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: #60000.
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: #60001.
But this PR has conflicts, please resolve them!

[ti-chi-bot]

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

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.5: #60003.