chore: add logging for CredentialsProviderError

[kuhe]

Enable access to the log of instantiated CredentialsProviderErrors.

In the AWS SDK with its many credential sources (default chain), the sequence through which you may end up with a certain provider in the chain is unclear, and seeing the history of thrown CredentialProviderErrors helps with both maintainer and user debugging.

Example log:

2024-05-23T20:17:57.283Z -> Not found in ENV: UA_APP_ID_ENV_NAME
2024-05-23T20:17:57.283Z -> Not found in ENV: AWS_DEFAULTS_MODE_ENV
2024-05-23T20:17:57.289Z -> Unable to find environment variable credentials.
2024-05-23T20:17:57.289Z -> Skipping SSO provider in default chain (inputs do not include SSO fields).
2024-05-23T20:17:57.296Z -> Not found in config files w/ profile [default]: UA_APP_ID_INI_NAME
2024-05-23T20:17:57.296Z -> Not found in config files w/ profile [default]: AWS_DEFAULTS_MODE_CONFIG
2024-05-23T20:17:57.297Z -> Profile some_profile could not be found or parsed in shared credentials file.
2024-05-23T20:17:57.299Z -> Profile default did not contain credential_process.
2024-05-23T20:17:57.301Z -> Web identity configuration not specified
2024-05-23T20:17:57.318Z -> Not found in ENV: ENV_ENDPOINT_URL
2024-05-23T20:17:57.318Z -> Not found in config files w/ profile [default]: CONFIG_ENDPOINT_URL
2024-05-23T20:17:57.318Z -> Not found in ENV: ENV_USE_FIPS_ENDPOINT, ENV
2024-05-23T20:17:57.318Z -> Not found in config files w/ profile [default]: CONFIG_USE_FIPS_ENDPOINT
2024-05-23T20:17:57.319Z -> Not found in ENV: ENV_USE_DUALSTACK_ENDPOINT, ENV
2024-05-23T20:17:57.319Z -> Not found in config files w/ profile [default]: CONFIG_USE_DUALSTACK_ENDPOINT
2024-05-23T20:17:57.321Z -> Not found in ENV: ENV_RETRY_MODE
2024-05-23T20:17:57.321Z -> Not found in config files w/ profile [default]: CONFIG_RETRY_MODE
2024-05-23T20:17:57.321Z -> Not found in ENV: ENV_MAX_ATTEMPTS
2024-05-23T20:17:57.321Z -> Not found in config files w/ profile [default]: CONFIG_MAX_ATTEMPTS

Example 2, debugging credential chain:

@aws-sdk/credential-provider-node defaultProvider::fromEnv
@aws-sdk/credential-provider-env - fromEnv
@smithy/property-provider -> Unable to find environment variable credentials.
@aws-sdk/credential-provider-node defaultProvider::fromSSO
@smithy/property-provider -> Skipping SSO provider in default chain (inputs do not include SSO fields).
@aws-sdk/credential-provider-node defaultProvider::fromIni
@aws-sdk/credential-provider-ini - fromIni
    default isAssumeRoleWithSourceProfile source_profile=cluster_role
@aws-sdk/credential-provider-ini - resolveAssumeRoleCredentials (STS)
@aws-sdk/credential-provider-ini - finding credential resolver using source_profile=[cluster_role]
    cluster_role isCredentialSourceProfile credential_source=EcsContainer
@aws-sdk/credential-provider-ini - resolveAssumeRoleCredentials (STS)
@aws-sdk/credential-provider-ini - finding credential resolver using profile=[cluster_role]
@aws-sdk/credential-provider-ini - credential_source is EcsContainer
@aws-sdk/credential-provider-http - fromHttp
@aws-sdk/client-sts::resolveRegion accepting first of: undefined (provider) undefined (parent client) us-east-1 (STS default)

[kuhe]

we were previously logging the Function.toString() value, which is quite unreadable...

[kuhe]

motivated by issue reported in #1288