branch-4.1: [chore](external) Upgrade Hive shade and align BE exec version

[suxiaogang223]

What problem does this PR solve?

Related PRs: #66809, #66685

branch-4.1 uses Paimon 1.4.2, but hive-catalog-shade 3.1.1 embeds Paimon 1.3 classes. The existing packaging workaround therefore removes org/apache/paimon/** and related service descriptors from the shade artifact and relies on separately managed Paimon dependencies.

hive-catalog-shade 3.1.2 now embeds Paimon 1.4.2, so the workaround is no longer needed.

In addition, external table sink hash routing on branch-4.1 currently uses BE execution version 12. Master reserves version 12 for Iceberg Variant compatibility and reserves version 13 for external sink hash routing in #66809. Release branches must use the same compatibility boundary.

What changed?

• Upgrade hive-catalog-shade from 3.1.1 to 3.1.2.
• Remove the dependency-order workaround and the direct paimon-hive-connector-3.1 dependency.
• Remove the Maven Ant repackaging step that strips org/apache/paimon/** and Paimon service descriptors.
• Move external table sink hash routing from BE execution version 12 to 13.
• Advance the FE and BE maximum execution version to 13 and document master's version 12 reservation.

Validation

• Verified XML syntax with xmllint.
• Verified Maven dependency resolution includes hive-catalog-shade:3.1.2 and Paimon 1.4.2 modules.
• Verified the Paimon core and Hive storage-handler classes embedded in hive-catalog-shade:3.1.2 match Paimon 1.4.2.
• Formatted the changed BE files with clang-format 16.0.6.
• Ran git diff --check.
• BE compilation was intentionally skipped because this change only updates compatibility constants and packaging metadata.

Release note

None

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

[suxiaogang223]

run buildall

[hello-stephen]

FE UT Coverage Report

Increment line coverage `` 🎉
Increment coverage report
Complete coverage report

[github-actions]

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

[github-actions]

PR approved by anyone and no changes requested.

[yiguolei]

skip buildall