[Enhancement] improve partial update by column mode overflow estimate strategy (backport #50300)

[mergify]

Why I'm doing:

In previous PR #49054, I introduced partial_update_memory_limit_per_worker to prevent ArrayColumn object overflow (larger than 4GB), but still some issue remain. Because I use the avg column data size to estimate how large ArrayColumn object can be, and it will still overflow when multi columns were updated and one of them is much larger than others.

What I'm doing:

Using whole rows in upt file to estimate how large ArrayColumn object instead of using the avg column data size. It may lead to overvalue but it's still better than undervalue which will lead to overflow.

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 #50300 done by [Mergify](https://mergify.com). ## Why I'm doing: In previous PR #49054, I introduced `partial_update_memory_limit_per_worker` to prevent `ArrayColumn` object overflow (larger than 4GB), but still some issue remain. Because I use the avg column data size to estimate how large `ArrayColumn` object can be, and it will still overflow when multi columns were updated and one of them is much larger than others.

What I'm doing:

Using whole rows in upt file to estimate how large ArrayColumn object instead of using the avg column data size. It may lead to overvalue but it's still better than undervalue which will lead to overflow.

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