[shuke987]

What problem does this PR solve?

Issue Number: None

Related PR: #65543

Problem Summary:

Backport the forced-replica-aware SHOW CREATE golden selection to branch-4.1. The branch-4.1 P0 environment forces OLAP tables to three replicas, while this case only had the one-replica golden. The master result file could not be cherry-picked directly because branch-4.1 does not emit binlog.format, so this backport preserves the complete branch-4.1 baseline and adds matching replica-1/replica-3 result blocks.

Release note

None

Check List (For Author)

• Test

  • Regression test
    • The target case passed with forced replica 3 while validating [fix](regression) Support forced replica golden in show create case #65543.
    • Verified all four replica-1 blocks preserve the branch-4.1 baseline, and each replica-3 block differs only in replication_allocation.
    • git diff --check passed.
  • 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?

[shuke987]

run buildall

[shuke987]

/review

[github-actions]

Static review completed for PR #65673. I did not find a blocking issue.

Checked:

• The Groovy suite computes the effective replica count from force_olap_table_replication_allocation before force_olap_table_replication_num, matching the FE forced-replica precedence.
• The dynamic quickRunTest tags line up with the new replica-1 and replica-3 golden blocks, and the regression output iterator skips unused alternate blocks safely.
• SHOW CREATE TABLE, rollup, and CREATE TABLE LIKE paths continue to serialize the default-tag replica allocation as expected for the intended branch-4.1 forced-replica case.
• The changed-file sweep covered both changed files. Existing inline comments: none. Additional user focus: none.

Validation: static review plus git diff --check on the prompted range passed. I did not run the regression suite in this runner. The main review, two normal subagents, and the risk-focused subagent all converged with NO_NEW_VALUABLE_FINDINGS, so no inline comments are proposed.

[yiguolei]

skip buildall