[fix](nereids) Block push-down of filters containing unique functions through Generate and CTE consumer

[yujun777]

What problem does this PR solve?

Issue Number: close #25201, close #25202

Problem Summary:
Two Nereids rewrite rules moved filter conjuncts that contain non-idempotent UniqueFunction calls (rand / uuid / random_bytes / uuid_numeric) across operators that change how many times the unique function is evaluated, producing wrong results.

1. PushDownFilterThroughGenerate pushed a conjunct like t1.id + rand(1,100) > 5 below LogicalGenerate. Before the push, rand is evaluated per generated row; after, it is evaluated per base row and then the result is duplicated for every row produced by generate, so groups of N generated rows share a single rand value instead of N independent ones.

2. CollectFilterAboveConsumer registered filter conjuncts above a CTE consumer into cascadesContext.putConsumerIdToFilter(...), after which RewriteCteChildren.tryToConstructFilter would OR them up and push them into the CTE producer. For a conjunct like rand() > 0.1, that causes the random filter to run on both the producer scan and each consumer filter, and different consumers would see inconsistent rows.

Fix: in both rules, skip conjuncts whose containsUniqueFunction() is true so they stay above the operator and are evaluated once per output row.

Adjacent rules (PushDownFilterThroughRepeat/Window/PartitionTopN/SetOperation, PullUpPredicates and its consumers) have the same class of bug but are out of scope for this PR and will be addressed separately.

Release note

Fix wrong results when filters containing non-idempotent functions (rand / uuid / random_bytes / uuid_numeric) are combined with LATERAL VIEW explode_* / LogicalGenerate or CTE consumers.

Check List (For Author)

• Test:
  • Regression test (new suites under regression-test/suites/nereids_rules_p0/unique_function/)
  • Unit Test (new PushDownFilterThroughGenerateTest and CollectFilterAboveConsumerTest under fe/fe-core/src/test/java/org/apache/doris/nereids/rules/rewrite/)
• Behavior changed: Yes. Filter conjuncts containing UniqueFunction are no longer pushed below LogicalGenerate and are no longer collected into a CTE producer. Deterministic conjuncts still behave as before.
• Does this need documentation: No.

[Thearas]

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
3. What features were added. Why was this function added?
4. Which code was refactored and why was this part of the code refactored?
5. Which functions were optimized and what is the difference before and after the optimization?

[yujun777]

run buildall

[yujun777]

/review

[hello-stephen]

FE UT Coverage Report

Increment line coverage 75.00% (3/4) 🎉
Increment coverage report
Complete coverage report

[github-actions]

OpenCode automated review failed and did not complete.

Error: Review step was skipped (possibly timeout or cancelled)
Workflow run: https://github.com/apache/doris/actions/runs/24768762135

Please inspect the workflow logs and rerun the review after the underlying issue is resolved.

[hello-stephen]

FE Regression Coverage Report

Increment line coverage 100.00% (4/4) 🎉
Increment coverage report
Complete coverage report

[starocean999]

/review

[github-actions]

PR approved by at least one committer and no changes requested.

[github-actions]

PR approved by anyone and no changes requested.

[github-actions]

{
"overall": "comment",
"verdict": "no_blocking_findings",
"findings": [],
"critical_checkpoints": {
"goal": "The PR goal is to stop moving filters that contain UniqueFunction calls through LogicalGenerate and through CTE-consumer collection. The changed rules accomplish that direct goal, and the added FE unit tests plus regression suites cover those direct paths.",
"minimality": "The modification is small, clear, and focused: each affected rule adds a narrow containsUniqueFunction guard without changing unrelated behavior.",
"concurrency": "No concurrency, locking, or lifecycle-sensitive state is involved in the touched code paths.",
"lifecycle": "No special lifecycle or initialization-order concerns were introduced.",
"config": "No configuration was added or changed.",
"compatibility": "No FE-BE protocol, storage-format, or rolling-upgrade compatibility surface was changed.",
"parallel_paths": "There are still adjacent optimizer paths of the same bug class mentioned in the PR description, but I did not find a blocking defect in the specific paths modified by this PR.",
"special_conditions": "The new containsUniqueFunction checks are appropriate here and consistent with existing Nereids safeguards in other pushdown/rewrite rules.",
"tests": "Direct rule coverage is present in FE unit tests and regression shape-plan tests. Residual risk: the new regression coverage is structural rather than runtime-result based.",
"test_results": "The new regression outputs are consistent with the added suites and appear auto-generated.",
"observability": "No additional observability is needed for this optimizer rewrite change.",
"transactions_persistence": "Not applicable.",
"data_writes": "Not applicable.",
"fe_be_variables": "Not applicable.",
"performance": "No obvious performance concern; the extra containsUniqueFunction checks are trivial.",
"other": "No additional blocking issue found in the touched code."
},
"focus_points": {
"user_focus": "No additional user-provided focus points.",
"response": "No extra issue was found beyond the general review."
},
"residual_risks": [
"The new regression coverage mainly checks plan shape, so it does not independently assert runtime row-set correctness for the wrong-result scenarios."
]
}