[BugFix] Fix unlimit delete_txn_log request from FE side (backport #54857)

[mergify]

Why I'm doing:

In share data mode, if we use batch publish, when the publish is finished, a deleteTxnLog task will be send
to BE from a thread pool. But in current impl, we just send the RPC request but not wait for its finishing.
It makes that many bthread stack of deleteTxnLog will be accumulated in BE side and if hit the limit max_map_count
of operation system, BE will completely stuck.

What I'm doing:

Wait the rpc call finished in thread pool

Fixes #issue

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

[mergify]

Cherry-pick of a6b14d7 has failed:

On branch mergify/bp/branch-3.3/pr-54857
Your branch is up to date with 'origin/branch-3.3'.

You are currently cherry-picking commit a6b14d75ae.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   fe/fe-core/src/main/java/com/starrocks/transaction/PublishVersionDaemon.java

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[mergify]

@mergify[bot]: Backport conflict, please reslove the conflict and resubmit the pr