fix: Ensure that custom KMS key is not created if encryption is not enabled, support computed values in cluster name

[csantanapr]

Description

• Ensure that custom KMS key is not created if encryption is not enabled
• Avoid throwing an index error when users provide their own custom launch template instead of the module creating a custom launch template
• Support instances where a computed value is passed into the cluster name, such as using random provider resources

Motivation and Context

• Currently, you could end up with a custom KMS key that is not used by the cluster if encryption is disabled
• Allow users to pass in computed values as the cluster name without error
• Resolves Upgrade 18.x --> 19.x- create_kms_key Provision Error #2321
• Resolved Error: error creating KMS Key: MalformedPolicyDocumentException #2325
• Closes fix: Ensure that custom KMS key is not created if encryption is not enabled, support computed values in cluster name #2318

Breaking Changes

• The default KMS key alias for the cluster name will be re-created but this is generally a safe process since its just an identifier. Otherwise, no breaking changes

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

[antonbabenko]

This PR is included in version 19.0.4 🎉

[jurgen-weber-deltatre]

We still ran into this error even thought we were on the fixed version so I feel there is more to it, as an alternative and if someone else ends up here please be aware you can use your own KMS key:

  create_kms_key                  = false # disable key creation
  cluster_encryption_config       = {
    resources: [
      "secrets"
    ],
    provider_key_arn              = "my kms key ARN"
  }

[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.