[Improvement](join) lazy calculate all_match_one

[BiteTheDDDDt]

What problem does this PR solve?

Sometimes we don't need to calculate all_match_one (for example, when no columns are materialized in probe_side_output_column)

      SELECT /*+ LEADING({store_sales date_dim} item) */
        any(iss.i_brand_id) brand_id
      , any(iss.i_class_id) class_id
      , any(iss.i_category_id) category_id
      FROM
        store_sales
      , item iss
      , date_dim d1
      WHERE (ss_item_sk = iss.i_item_sk)
         AND (ss_sold_date_sk = d1.d_date_sk)
         AND (d1.d_year BETWEEN 1999 AND (1999 + 2));

before:

after:

Check List (For Author)

• Test

  • Regression test
  • Unit Test
  • Manual test (add detailed scripts or steps below)
  • No need to test or manual test. Explain why:
    • This is a refactor/code format and no logic has been changed.
    • Previous test can cover this change.
    • No code files have been changed.
    • Other reason

• Behavior changed:

  • No.
  • Yes.

• Does this need documentation?

  • No.
  • Yes.

Check List (For Reviewer who merge this PR)

• Confirm the release note
• Confirm test cases
• Confirm document
• Add branch pick label

[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?

[BiteTheDDDDt]

run buildall

[hello-stephen]

BE UT Coverage Report

Increment line coverage 100.00% (13/13) 🎉

Increment coverage report
Complete coverage report

Category	Coverage
Function Coverage	53.34% (18634/34932)
Line Coverage	39.02% (172143/441207)
Region Coverage	33.62% (133264/396431)
Branch Coverage	34.58% (57373/165891)

[hello-stephen]

BE Regression && UT Coverage Report

Increment line coverage 100.00% (13/13) 🎉

Increment coverage report
Complete coverage report

Category	Coverage
Function Coverage	72.27% (24754/34254)
Line Coverage	58.96% (259891/440828)
Region Coverage	53.97% (216541/401251)
Branch Coverage	55.45% (92489/166790)

[HappenLee]

LGTM

[github-actions]

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

[github-actions]

PR approved by anyone and no changes requested.

[mrhhsg]

lgtm