[Fix](p0) Deduplicate table names to avoid cross-suit drops

[linrrzqqq]

What problem does this PR solve?

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

In some python_udf p0 tests, two tables with the same name exist under the same database, and one was just created when the other was tested and dropped.

2026-02-02 18:53:05.163 INFO [suite-thread-16] (Suite.groovy:572) - Execute sql: DROP TABLE IF EXISTS test_conditional_module;

...

Exception in pythonudtf_p0/test_pythonudtf_exceptions_module.groovy(line 445):
    
            sql """
            INSERT INTO test_conditional_module VALUES 
            (1, -10),
            (2, 0),
            (3, 50),
            (4, 200),
            (5, NULL);
            """
            
            qt_conditional_process """
    ^^^^^^^^^^^^^^^^^^^^^^^^^^ERROR LINE^^^^^^^^^^^^^^^^^^^^^^^^^^
                SELECT id, tmp.input, tmp.category, tmp.result
                FROM test_conditional_module
                LATERAL VIEW udtf_conditional_process_module(val) tmp AS input, category, result
                ORDER BY id;
            """
            
            // Test 6.2: Yield Control - No Output Case
            sql """ DROP FUNCTION IF EXISTS udtf_filter_yield_module(INT); """
            sql """
            CREATE TABLES FUNCTION udtf_filter_yield_module(INT)
    
Exception:  java.sql.SQLException: errCode = 2, detailMessage = Table [test_conditional_module] does not exist in database [regression_test_pythonudtf_p0].(line 3, pos 17)

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?

[linrrzqqq]

run buildall

[github-actions]

PR approved by anyone and no changes requested.

[github-actions]

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