feat(source): use the default_provider for kinesis (#17849)

[psheets]

…ential provider chain

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

17849
Updated Kinesis source to use k8s service accounts.

• build_credential_provider - updated to changed to async and made it use the default_provider if access_key and secret_key were not provided.

Checklist

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• I have added test labels as necessary. See details.
• I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
• My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
• All checks passed in ./risedev check (or alias, ./risedev c)
• My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

• My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

• My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

aws.credentials.access_key_id and aws.credentials.secret_access_key are no longer required for the Kinesis source. Not providing them will make the connector fallback to the aws default_provider.

[xiangjinwu]

Related: #11086 (Resolved by #11120)

[fuyufjh]

Hi, @psheets I modified this PR a bit to add an environment variable to disable this function. Opened a new one #17933 because GitHub doesn't allow me to commit on your branch