[improvement](fe) Support hour-offset date_add/date_sub in MTMV partition rollup

[hakanuzum]

What problem does this PR solve?

Issue Number: close #62395

Related PR: None

Problem Summary:
MTMV partition rollup only handled date_trunc(partition_col, unit). It could not track partition lineage when the MV partition expression uses hour offset conversion such as:

• date_trunc(date_add(k2, INTERVAL 3 HOUR), 'day')
• date_trunc(date_sub(k2, INTERVAL 3 HOUR), 'day')

This is needed for UTC-storage and local-day partitioning workflows.

Release note

Support MTMV partition rollup and partition increment check for
date_trunc(date_add/date_sub(partition_col, INTERVAL N HOUR), unit).

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

Manual test steps:

• FE build: MVN_OPT='-Dmaven.build.cache.enabled=false' ./build.sh --fe --clean -j$(nproc)

• FE UT: ./run-fe-ut.sh --run org.apache.doris.mtmv.MTMVRelatedPartitionDescRollUpGeneratorTest

• Regression case command: ./run-regression-test.sh --run -d mtmv_p0 -s test_rollup_partition_mtmv_date_add

• Note: regression case requires running FE/BE regression cluster. Local run failed with connection refused when cluster was not started.

• Behavior changed:

  • No.
  • Yes. date_trunc(date_add/date_sub(...), unit) lineage is now supported for MTMV partition rollup/increment check.

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

[hakanuzum]

run buildall