[improvement](be) Support nested aggregate pushdown

[Gabriel39]

What problem does this PR solve?

Issue Number: close #xxx

Related PR: #xxx

Problem Summary: Support MIN/MAX aggregate pushdown for projected struct leaf columns in TableReader and FileReader by carrying FieldProjection through aggregate requests/results and resolving Parquet statistics at the projected leaf.

Release note

None

Check List (For Author)

• Test: Unit Test
  • Ran build-support/clang-format.sh be/src/format/reader/file_reader.h be/src/format/reader/table_reader.h be/src/format/new_parquet/parquet_reader.cpp be/test/format/reader/table_reader_test.cpp
  • Ran git diff --check
  • Attempted ./run-be-ut.sh --run '--filter=TableReaderTest.PushDownMinMaxFromProjectedStructLeaf:TableReaderTest.PushDownMinMaxFromNewParquetReader:TableReaderTest.PushDownMinMaxFallsBackWithoutDirectFileMapping', blocked because JAVA_HOME points to JDK 11 and JDK_17 is not set
• Behavior changed: Yes, MIN/MAX aggregate pushdown can use supported projected struct leaf statistics
• Does this need documentation: No

What problem does this PR solve?

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

Release note

None

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

[hello-stephen]

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?