[test](mtmv)Add mtmv up and down with drop table test case

[zfr9527]

testAdd mtmv up and down with drop table test case

Build the basic information. When conceiving upgrade and downgrade test cases, you should firmly grasp the object
representation of the function in the FE meta.
Taking MTMV as an example, the main function points are creation, refresh, and rewriting, and the involved entities
are the base table and MTMV.

1. When creating an MTMV, check if the rewriting meets the expectations.
2. When refreshing an MTMV, check if the rewriting meets the expectations.
3. When deleting an MTMV, check if the rewriting meets the expectations.
4. When deleting a base table, check if the rewriting meets the expectations; then trigger a refresh and check if the
   rewriting meets the expectations.
5. When deleting a partition of a base table, check if the rewriting meets the expectations; then trigger a refresh and
   check if the rewriting meets the expectations.
6. Design a slightly more complex scenario. For example: Build an MTMV with two base tables. When deleting one of the
   base tables, check if the refresh of the MTMV meets the expectations and if the rewriting meets the expectations;
   create an MTMV with the undeleted base table and check if it can be created and refreshed normally, and if the
   corresponding rewriting meets the expectations.

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

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