[feature](iceberg) support s3 tables

[morningman]

What problem does this PR solve?

This pull request introduces several changes to the project, primarily focusing on adding support for S3 tables in the Iceberg catalog and updating dependencies. The most significant changes include updating the pom.xml files, adding a new catalog type for S3 tables, and implementing a custom AWS credentials provider.

Dependency Updates:

• fe/fe-core/pom.xml: Added dependencies for software.amazon.awssdk:s3tables, software.amazon.s3tables:s3-tables-catalog-for-iceberg, and software.amazon.awssdk:sdk-core.
• fe/pom.xml: Updated doris.hive.catalog.shade.version to 2.1.3, iceberg.version to 1.6.1, and added s3tables.catalog.version set to 0.1.4. [1] [2] [3]

Code Changes for S3 Tables Support:

• fe/fe-core/src/main/java/org/apache/doris/datasource/iceberg/IcebergExternalCatalog.java: Added ICEBERG_S3_TABLES constant.
• fe/fe-core/src/main/java/org/apache/doris/datasource/iceberg/IcebergExternalCatalogFactory.java: Added a case for ICEBERG_S3_TABLES to create an IcebergS3TablesExternalCatalog instance.
• fe/fe-core/src/main/java/org/apache/doris/datasource/iceberg/IcebergS3TablesExternalCatalog.java: Implemented the IcebergS3TablesExternalCatalog class to support S3 tables.
• fe/fe-core/src/main/java/org/apache/doris/datasource/iceberg/s3tables/CustomAwsCredentialsProvider.java: Implemented a custom AWS credentials provider.

Additional Changes:

• fe/fe-core/src/main/java/org/apache/doris/datasource/iceberg/source/IcebergScanNode.java: Added a case for ICEBERG_S3_TABLES in the IcebergScanNode constructor.
• fe/fe-core/src/main/java/org/apache/doris/persist/gson/GsonUtils.java: Registered IcebergS3TablesExternalCatalog for Gson serialization. [1] [2]
• fe/fe-core/src/test/java/org/apache/doris/datasource/s3tables/S3TablesTest.java: Added a test class for S3 tables catalog functionality.

These changes collectively enhance the project's capability to manage S3 tables within the Iceberg catalog, along with updating necessary dependencies to ensure compatibility and functionality.

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?

[morningman]

run buildall