[BugFix] Fix sync publish failed after BE restart (backport #51045)

[mergify]

Why I'm doing:

We will return publish success after tablet apply finished if we enable sync publish to avoid waiting apply during query. However, if BE restart, we will return publish success even though the apply is not finished. So the query may get query time out issue after BE restarted.

The reason is the transaction related tablets is lost after BE restart. For primary key table, if BE receive publish request, BE will delete committed rowset meta and rewrite rowset meta into TabletMeta, so the transaction related tablet info are lost if we restart BE during waiting apply finished.

What I'm doing:

If BE restarted, add the tablet which max_readable_version less than request_version into error_tablet_ids. Then the transaction will be visible until all those tablets apply finished.

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

Bugfix cherry-pick branch check:

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

---

This is an automatic backport of pull request #51045 done by [Mergify](https://mergify.com). ## Why I'm doing: We will return publish success after tablet apply finished if we enable sync publish to avoid waiting apply during query. However, if BE restart, we will return publish success even though the apply is not finished. So the query may get `query time out` issue after BE restarted.

The reason is the transaction related tablets is lost after BE restart. For primary key table, if BE receive publish request, BE will delete committed rowset meta and rewrite rowset meta into TabletMeta, so the transaction related tablet info are lost if we restart BE during waiting apply finished.

What I'm doing:

If BE restarted, add the tablet which max_readable_version less than request_version into error_tablet_ids. Then the transaction will be visible until all those tablets apply finished.

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