branch-3.1: [chore](tde) Add scoped KMS credentials to regression clusters #64564

[Yukang-Lian]

What problem does this PR solve?

Issue Number: None

Related PR: #64564

Problem Summary: Backport scoped AWS and Aliyun KMS credential plumbing from #64564 to branch-3.1.

The change carries the four TDE credential values from regression-framework options through doris-compose into FE environment variables. Sensitive command arguments are masked in logs. The backport preserves the branch's existing cluster options and command execution model.

The branch is rebased onto the latest branch-3.1.

Release note

Allow regression clusters to receive scoped AWS and Aliyun KMS credentials for TDE tests.

Check List (For Author)

• Test: Manual / static validation
  • Python AST parsing passed for the changed compose Python modules
  • bash -n docker/runtime/doris-compose/resource/init_fe.sh: passed
  • Credential plumbing and sensitive-argument masking checks: passed
  • git diff --check: passed
  • Hosted CI is requested with run buildall
• Behavior changed: Yes
  • Adds optional scoped KMS credentials to regression cluster startup
  • Does not change production defaults when the options are unset
• Does this need documentation: No

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

[Yukang-Lian]

run buildall