[BugFix] fix column overflow when handle too large partial update

[luohaha]

Why I'm doing:

In current implementation, when handle partial column update, we will try to build the column to be updated with segment granularity, it will lead to overflow. E.g.

1. If we have a ARRAY column to be update, In the beginning, because the data in the table does not contain arrays yet, we will slice the segment file with a size of 1GB, so a segment file may contain a large number of rows. We can assume that there are 500w rows in a tablet.
2. And in a ArraryColumn struct, we store offset of array using uint32_t , that means we can only have 4,294,967,295 items in a ArraryColumn.
3. When items in one array is larger than 900, which is large than 4,294,967,295, so overflow happens.

What I'm doing:

Processing updates involving large amounts of data in batches, each batch will be limit by partial_update_memory_limit_per_worker.

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

[wyb]

cloud native table also need this optimization?

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

[FE Incremental Coverage Report]

✅ pass : 0 / 0 (0%)

[github-actions]

[BE Incremental Coverage Report]

✅ pass : 44 / 48 (91.67%)

file detail

	path	covered_line	new_line	coverage	not_covered_line_detail
🔵	be/src/storage/rowset/horizontal_update_rowset_writer.cpp	0	4	00.00%	[65, 66, 67, 68]
🔵	be/src/storage/rowset_column_update_state.cpp	39	39	100.00%	[]
🔵	be/src/storage/rowset_column_update_state.h	1	1	100.00%	[]
🔵	be/src/storage/rowset/rowset_writer.cpp	1	1	100.00%	[]
🔵	be/src/storage/rowset/rowset.h	2	2	100.00%	[]
🔵	be/src/storage/rowset/rowset_meta.h	1	1	100.00%	[]

[github-actions]

@Mergifyio backport branch-3.3

[github-actions]

@Mergifyio backport branch-3.2

[mergify]

backport branch-3.3

✅ Backports have been created

• #49477 [BugFix] fix column overflow when handle too large partial update (backport #49054) has been created for branch branch-3.3 but encountered conflicts

[mergify]

backport branch-3.2

✅ Backports have been created

• #49478 [BugFix] fix column overflow when handle too large partial update (backport #49054) has been created for branch branch-3.2 but encountered conflicts