fix: Usage of managed streaming kafka credentials

[sassdavid]

Description

For Managed Streaming for Kafka credentials, both client_certificate_tls_auth and sasl_scram_512_auth are optional. The current implementation does not allow using only one of them independently.

Motivation and Context

After this change, the following code will be valid for source_parameters:

source_parameters = {
  managed_streaming_kafka_parameters = {
    topic_name = var.input_kafka_topic
    batch_size = 10
    credentials = {
      sasl_scram_512_auth = var.msk_secret_arn
    }
  }
}

Currently, only the following form is accepted:

source_parameters = {
  managed_streaming_kafka_parameters = {
    topic_name = var.input_kafka_topic
    batch_size = 10
    credentials = {
      sasl_scram_512_auth         = var.msk_secret_arn
      client_certificate_tls_auth = valid_arn
    }
  }
}

Breaking Changes

No.

How Has This Been Tested?

• I have updated at least one of the examples/* to demonstrate and validate my change(s)
• I have tested and validated these changes using one or more of the provided examples/* projects

• I have executed pre-commit run -a on my pull request

[sassdavid]

Hi @antonbabenko ,
Can you help me review the PR? Maybe point in the right direction if something should be done differently.

[antonbabenko]

This PR is included in version 3.17.1 🎉

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.