[opt](mtmv) Support any_value aggregate function rollup rewrite when exsits aggregate materialized view

[seawinde]

What problem does this PR solve?

Support any_value rewrite when aggregate materialized view
Such as mv def sql is as following

select
o_orderdate,
any_value(l_partkey),
o_orderstatus,
l_suppkey,
any_value(l_suppkey),
any_value(o_orderstatus)
from lineitem_2
left join orders_2 on l_orderkey = o_orderkey and l_shipdate = o_orderdate
where l_partkey =3group by
o_orderstatus,
o_orderdate,
l_partkey,
l_suppkey;

the query like following can be rewritten scuucessfully by mv above

select
any_value(l_partkey),
any_value(l_suppkey),
any_value(o_orderstatus)
from lineitem_2
left join orders_2
on l_orderkey = o_orderkey and l_shipdate = o_orderdate
where l_partkey =3and o_orderstatus ='o'group by
o_orderdate,
l_suppkey;

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

Release note

Support any_value aggregate function rollup rewrite when exsits aggregate 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

[github-actions]

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

[github-actions]

PR approved by anyone and no changes requested.