[kafka/internal, kafkaexporter, kafkareceiver] Add SASL mechanism "AWS_MSK_IAM_OAUTHBEARER" to kafkaexporter

[donald-cheung]

Description:
This PR added the SASL mechanism "AWS_MSK_IAM_OAUTHBEARER" to kafkaexporter and kafkareceiver. This mechanism use the AWS MSK IAM SASL Signer for Go /~https://github.com/aws/aws-msk-iam-sasl-signer-go. This mechanism is added because the "AWS_MSK_IAM" is not working in our cluster and also in this issue. We added an new mechanism instead of replace the existing one because we want to keep the backward compatibility just in case someone is using "AWS_MSK_IAM".

Link to tracking Issue:
19747

Testing:
We built the images and tested the SASL mechanism in our team.
We added related unit tests.

Documentation:
We updated the kafkaexporter and kafakreciever README on the SASL mechanism.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: donald-cheung / name: Donald Cheung (Woven by Toyota, Inc.) (fd12dd2, 7955f9d, b4c0c73, ddda641, bad9c2e, f6148a6, e934bc0, 1c502fd, c14de4e, e9ecbc1, a35c776, 154dfe8, c25c058, 596c814, 2c803f1, b5ffb5a, e0f68d7, f3c9057, f3f2c39, 897d705, daf479b, fa288ba)
• ✅ login: MovieStoreGuy / name: Sean Marciniak (15bd9f9)

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[mx-psi]

@donald-cheung Thanks for your contribution! We need to you to sign the CLA in order to be able to accept your contribution

[donald-cheung]

@mx-psi
Thanks for the reminder. I am asking my company to sign the CCLA so it will take some time.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[github-actions]

Closed as inactive. Feel free to reopen if this PR is still being worked on.

[mattiasnensen]

Hey, this would be awesome to have. What's going on?

[donald-cheung]

Sorry, we are in the process of getting approval from the upper organization. This will take some time. Thank you.

[donald-cheung]

We will have a meeting and update the progress next week.
BTW, how can I reopen this PR? There is no button in the bottom. Thank you.

[mx-psi]

@donald-cheung Let me know when you have approval from your org and want to reopen the PR and I can do it for you :)

[donald-cheung]

@mx-psi Thanks. The meeting is rescheduled to next week so I will update you later.

[canhnt]

Hi @donald-cheung, could you please keep posted on the result? This MR is useful for us.

[donald-cheung]

Sorry for the late reply. The feedback from the upper organization is good. The upper organization will start their procedures to approve.

[donald-cheung]

Hello @mx-psi @pavolloffay @MovieStoreGuy, do you have any schedule to merge this PR? Thank you.

[amal-v]

Waiting so long for on this PR. Can we get some traction here ? @jpkrohling

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[donald-cheung]

Hello @mx-psi @pavolloffay @MovieStoreGuy, can I get some updates on the schedule to merge this PR? Thank you.

[hicwic]

+1 for merging. waiting this functionnality

[golem1987]

Waiting for merging, need this functionality

[MovieStoreGuy]

I have a few environment questions for you @donald-cheung ,

How was the performance of using the new auth provider? Did it cause any additional resource usage on the kafka cluster?
When I originally looked at IAM auth, the team and I roughly saw a significant increase on load due to the new auth, I was wondering if your tests showed the same.

[donald-cheung]

I have a few environment questions for you @donald-cheung ,

How was the performance of using the new auth provider? Did it cause any additional resource usage on the kafka cluster? When I originally looked at IAM auth, the team and I roughly saw a significant increase on load due to the new auth, I was wondering if your tests showed the same.

Hello, can you provide more details on your test? We are trying to see if the increase on load also happens on our side.