[Enhancement](recycler) Add valid s3 vault config for recycler

[Yukang-Lian]

What problem does this PR solve?

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

In the current multi-vault mode, deleting vaults is not allowed. This causes the recycler to still attempt accessing invalid vaults when deleting data, slowing down the deletion process. The HDFS accessor automatically checks the connectivity of vaults during initialization and only initializes connected HDFS vaults. However, S3 does not check if vaults are connected and initializes all vaults, including invalid ones. This PR adds a configuration that allows users to specify valid S3 vaults. If configured, only the endpoints listed in this vector will be initialized when initializing S3 vaults.

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

[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

[doris-robot]

TeamCity cloud ut coverage result:
Function Coverage: 82.33% (1062/1290)
Line Coverage: 65.85% (17552/26654)
Region Coverage: 65.35% (8658/13249)
Branch Coverage: 55.23% (4667/8450)
Coverage Report: http://coverage.selectdb-in.cc/coverage/5bb603faeb9a6dbfb07b9aec23b66c051aaae241_5bb603faeb9a6dbfb07b9aec23b66c051aaae241_cloud/report/index.html

[Yukang-Lian]

run buildall

[doris-robot]

TeamCity cloud ut coverage result:
Function Coverage: 82.40% (1063/1290)
Line Coverage: 66.02% (17599/26658)
Region Coverage: 65.43% (8670/13250)
Branch Coverage: 55.30% (4673/8450)
Coverage Report: http://coverage.selectdb-in.cc/coverage/e2309c4831a79b58f675588bd375d16c4bdeb075_e2309c4831a79b58f675588bd375d16c4bdeb075_cloud/report/index.html

[gavinchou]

request change

[Yukang-Lian]

run buildall

[Yukang-Lian]

run buildall

[doris-robot]

TeamCity cloud ut coverage result:
Function Coverage: 82.40% (1063/1290)
Line Coverage: 66.09% (17618/26659)
Region Coverage: 65.54% (8684/13250)
Branch Coverage: 55.42% (4683/8450)
Coverage Report: http://coverage.selectdb-in.cc/coverage/abf1e5a1dd23e582843305ca4922952f240b25a4_abf1e5a1dd23e582843305ca4922952f240b25a4_cloud/report/index.html

[Yukang-Lian]

run cloud_p0

[Yukang-Lian]

run buildall

[doris-robot]

TeamCity cloud ut coverage result:
Function Coverage: 82.28% (1063/1292)
Line Coverage: 65.86% (17600/26723)
Region Coverage: 65.37% (8674/13270)
Branch Coverage: 55.28% (4677/8460)
Coverage Report: http://coverage.selectdb-in.cc/coverage/c17c494ac5cb5f49cb1a2d8e02dd09319729678b_c17c494ac5cb5f49cb1a2d8e02dd09319729678b_cloud/report/index.html

[Yukang-Lian]

run cloud_p0