server,session: make sure ResultSet.Close() errors return to the client (#48447)

[ti-chi-bot]

This is an automated cherry-pick of #48447

What problem does this PR solve?

Issue Number: close #48446, ref #48411

Problem Summary:

What is changed and how it works?

This also fix #48411 in another way, and can prevent more bugs.

Close the result set after all rs.Next(), and before cc.writeEOF()
Avoid the case that error happen and can't be sent to the client after writeEOF.

Check List

Tests

The test code in #48412 should also apply for this one, as the both can fix #48411, so I don't bother writer another duplicated test.

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

See #48411

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

None

[YangKeao]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: crazycs520, YangKeao

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 [YangKeao,crazycs520]

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:

• 2023-11-10 05:35:22.038390144 +0000 UTC m=+3795319.625500289: ☑️ agreed by crazycs520.
• 2023-11-10 05:36:17.768836538 +0000 UTC m=+3795375.355946876: ☑️ agreed by YangKeao.

[hawkingrei]

/retest