fix(credential-provider-http): fix logger binding issue

[smilkuri]

Issue

#7297

Description

• FromHttpOptions extends CredentialProviderOptions which has an optional Logger interface. When users provide class-based logger without binding breaks the this context resulting in Cannot read properties of undefined errors, if the logger is an object that references other members.
• Added .bind(options.logger) to preserve method context.

Testing

Locally

yarn test:all
Tasks:    516 successful, 516 total
Cached:    516 cached, 516 total
  Time:    25.9s >>> FULL TURBO

 PASS  packages/signature-v4-crt/src/CrtSignerV4.spec.ts
 PASS  packages/signature-v4-crt/src/crtSuite.spec.ts

Test Suites: 2 passed, 2 total
Tests:       25 passed, 25 total
Snapshots:   0 total
Time:        4.837 s, estimated 5 s
Ran all test suites.
lerna notice cli v5.5.2
lerna notice filter including "@aws-sdk/{fetch-http-handler,hash-blob-browser}"
lerna info filter [ '@aws-sdk/{fetch-http-handler,hash-blob-browser}' ]
lerna ERR! EFILTER No packages remain after filtering [ '@aws-sdk/{fetch-http-handler,hash-blob-browser}' ]

Checklist

• [n/a] If the PR is a feature, add integration tests (*.integ.spec.ts).
• [n/a ] If you wrote E2E tests, are they resilient to concurrent I/O?
• [n/a] If adding new public functions, did you add the @public tag and enable doc generation on the package?

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[kuhe]

Suggested change

	options.logger?.constructor?.name === "NoOpLogger" || !options.logger
	options.logger?.constructor?.name === "NoOpLogger" || !options.logger?.warn

our types assume when logger exists, logger.warn exists, but let's be safe here. Some users have passed incomplete loggers in the past.

[kuhe]

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

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.