feat(catalog): avoid static global credentials provider

[Gezi-lzq]

Refactors CredentialProviderHolder to prevent "Connection Pool Shutdown" errors by creating a new provider instance upon each invocation of create().

Previously, a single static AwsCredentialsProvider was shared globally. If this provider was closed, it would affect all subsequent operations. By creating a new provider on each create() call from Iceberg, this change removes the global singleton and isolates provider instances.

Fixes #2680

apache/iceberg#8677

How do I fix "java.lang.IllegalStateException: Connection pool shut down" error?

You attempted to use the credentials provider returned from DefaultCredentialsProvider#create() after it was closed. DefaultCredentialsProvider#create returns a singleton instance, so if it's closed and your code calls the resolveCredentials method, the exception is thrown after cached credentials (or token) expire.

https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/troubleshooting.html#faq-connection-pool-shutdown-exception

[Copilot]

Pull Request Overview

This PR refactors the CredentialProviderHolder class to eliminate the use of a static global credentials provider singleton and instead create a new provider instance on each create() method invocation. This change prevents "Connection Pool Shutdown" errors that occur when a shared static AWS credentials provider is closed, affecting all subsequent operations.

• Removed static provider field and replaced with bucketURI storage
• Modified create() method to invoke providerSupplier.apply(bucketURI) for fresh provider instances
• Updated setup(BucketURI) method to store the bucketURI instead of creating a provider immediately