fix(expr): evaluate scalar expr non-strictly in streaming

[wangrunji0408]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

fix #12474

Checklist

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• I have added test labels as necessary. See details.
• I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
• My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
• All checks passed in ./risedev check (or alias, ./risedev c)
• My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

• My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

• My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

[BugenZhao]

LGTM

[wangrunji0408]

@BugenZhao any ideas on how to rewrite e2e_test/error_ui/simple/recovery.slt? one option is to switch to another bug #11915 for now. 🤪

[BugenZhao]

@BugenZhao any ideas on how to rewrite e2e_test/error_ui/simple/recovery.slt? one option is to switch to another bug #11915 for now. 🤪

Sure. Let's use that as a workaround until we find a good approach to reliably trigger a meaningful failure.

[wangrunji0408]

What about introducing a test-only function rw_panic()?

[BugenZhao]

What about introducing a test-only function rw_panic()?

We already have a RECOVERY command to tigger a recovery on meta, and I've also attempted to add a command to trigger a failure on compute node (#16397 (comment)).

However, as this test also covers the root cause identification (#16431), I'm afraid whether a manually-triggered failure is general enough. 🤔