[BugFix] Fix transaction stream load lock leak (backport #53564)

[mergify]

Why I'm doing:

In transaction stream load, a normal load request needs to go through the on_header, on_chunk_data, and handle processes of the TransactionStreamLoadAction. To prevent concurrent load requests, a lock will be acquired in on_header, and released in handle. But for an abnormal load request, handle may be not called, and the lock will not be released. For example, the client crashes after transmitting a part of data, only on_header and on_chunk_data are called, and handle will not be called. This can lead to resources not being cleaned up after the load timeout because the cleanup needs acquire the lock (see TransactionMgr::_clean_stream_context).

What I'm doing:

Move the lock release to TransactionStreamLoadAction::free_handler_ctx which will be always called regardless of whether an exception occurs or not.

Fixes #53155

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• Yes, this PR will result in a change in behavior.
• No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• Interface/UI changes: syntax, type conversion, expression evaluation, display information
• Parameter changes: default values, similar parameters but with different default values
• Policy changes: use new policy to replace old one, functionality automatically enabled
• Feature removed
• Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• I have added test cases for my bug fix or my new feature
• This pr needs user documentation (for new or modified features or behaviors)
  • I have added documentation for my new feature or new function
• This is a backport pr

Bugfix cherry-pick branch check:

• I have checked the version labels which the pr will be auto-backported to the target branch
  • 3.4
  • 3.3
  • 3.2
  • 3.1
  • 3.0

    ---

    This is an automatic backport of pull request [BugFix] Fix transaction stream load lock leak #53564 done by Mergify.

Why I'm doing:

In transaction stream load, a normal load request needs to go through the on_header, on_chunk_data, and handle processes of the TransactionStreamLoadAction. To prevent concurrent load requests, a lock will be acquired in on_header, and released in handle. But for an abnormal load request, handle may be not called, and the lock will not be released. For example, the client crashes after transmitting a part of data, only on_header and on_chunk_data are called, and handle will not be called. This can lead to resources not being cleaned up after the load timeout because the cleanup needs acquire the lock (see TransactionMgr::_clean_stream_context).

What I'm doing:

Move the lock release to TransactionStreamLoadAction::free_handler_ctx which will be always called regardless of whether an exception occurs or not.

Fixes #53155

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• Yes, this PR will result in a change in behavior.
• No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• Interface/UI changes: syntax, type conversion, expression evaluation, display information
• Parameter changes: default values, similar parameters but with different default values
• Policy changes: use new policy to replace old one, functionality automatically enabled
• Feature removed
• Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• I have added test cases for my bug fix or my new feature
• This pr needs user documentation (for new or modified features or behaviors)
  • I have added documentation for my new feature or new function
• This is a backport pr