[fix](mtmv) Fix materialized view not chosen by cbo when join is rewritten by materialized view

[seawinde]

What problem does this PR solve?

        Such query as following:

                          s_acctbal,
                          s_name,
                          n_name,
                          p_partkey,
                          p_mfgr,
                          s_address,
                          s_phone,
                          s_comment
                        FROM
                          part,
                          supplier,
                          partsupp,
                          nation,
                          region
                        WHERE
                          p_partkey = ps_partkey
                          AND s_suppkey = ps_suppkey
                          AND s_nationkey = n_nationkey
                          AND n_regionkey = r_regionkey
                          AND r_name = 'EUROPE';

         If query can be rewritten by materialized view as following:

                          s_acctbal,
                          s_name,
                          n_name,
                          p_partkey,
                          p_mfgr,
                          s_address,
                          s_phone,
                          s_comment
                        FROM
                          mv,
                          region
                        WHERE
                          p_partkey = ps_partkey
                          AND s_suppkey = ps_suppkey
                          AND p_size = 15
                          AND p_type LIKE '%BRASS'
                          AND s_nationkey = n_nationkey
                          AND n_regionkey = r_regionkey
                          AND r_name = 'EUROPE';

The cost of mv scan factor should be lower, because the rewrite has obvious benefit.

Related PR: #xxx

Problem Summary:
Fix materialized view not chosen by cbo when join is rewritten by materialized view

Release note

Fix materialized view not chosen by cbo when join is rewritten by materialized view

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

[doris-robot]

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?

[seawinde]

run buildall

[seawinde]

run buildall