[BugFix] fix array_map's error result when inputs are constant (backport #51833)

[mergify]

Why I'm doing:

What I'm doing:

Fixes https://github.com/StarRocks/StarRocksTest/issues/8662

introduced by: #51244

for scenarios where all inputs are constant, we will directly evaluate lambda expr based on the const column to avoid extra overhead. In this case, we will not unpack the const column or align the offset with capture columns.
However, there is an exception, such as array_map(x->array_length(x) > c1+1, [[1,2,3]]), where the lambda expression depends on other capture columns. In this case, we cannot follow the above strategy and still need to unpack the const and follow the normal process, otherwise it will get a wrong result.
in this pr, I fixed it.

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 #51833 done by [Mergify](https://mergify.com). ## Why I'm doing:

What I'm doing:

Fixes https://github.com/StarRocks/StarRocksTest/issues/8662

introduced by: #51244

for scenarios where all inputs are constant, we will directly evaluate lambda expr based on the const column to avoid extra overhead. In this case, we will not unpack the const column or align the offset with capture columns.
However, there is an exception, such as array_map(x->array_length(x) > c1+1, [[1,2,3]]), where the lambda expression depends on other capture columns. In this case, we cannot follow the above strategy and still need to unpack the const and follow the normal process, otherwise it will get a wrong result.
in this pr, I fixed it.

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