fix(credential-provider-node): fix logger binding issue (#7302)

Author: smilkuri

packages/credential-provider-http/src/fromHttp/fromHttp.ts

@@ -28,7 +28,9 @@ export const fromHttp = (options: FromHttpOptions = {}): AwsCredentialIdentityPr
   const tokenFile = options.awsContainerAuthorizationTokenFile ?? process.env[AWS_CONTAINER_AUTHORIZATION_TOKEN_FILE];
 
   const warn: (warning: string) => void =
-    options.logger?.constructor?.name === "NoOpLogger" || !options.logger ? console.warn : options.logger.warn;
+    options.logger?.constructor?.name === "NoOpLogger" || !options.logger?.warn
+      ? console.warn
+      : options.logger.warn.bind(options.logger);
 
   if (relative && full) {
     warn(

packages/credential-provider-node/src/defaultProvider.ts

@@ -70,7 +70,9 @@ export const defaultProvider = (init: DefaultProviderInit = {}): MemoizedProvide
           if (envStaticCredentialsAreSet) {
             if (!multipleCredentialSourceWarningEmitted) {
               const warnFn =
-                init.logger?.warn && init.logger?.constructor?.name !== "NoOpLogger" ? init.logger.warn : console.warn;
+                init.logger?.warn && init.logger?.constructor?.name !== "NoOpLogger"
+                  ? init.logger.warn.bind(init.logger)
+                  : console.warn;
               warnFn(
                 `@aws-sdk/credential-provider-node - defaultProvider::fromEnv WARNING:
     Multiple credential sources detected: