Make service account key path as variable

[goruha]

what

• Made service account key path as variable

why

• Different charts use different variables.yaml structure,
  for some you use serviceAccount key path for annotations but other use rbac.serviceAccount.

[goruha]

/test all

[aknysh]

one comment

[korenyoni]

This new variable should also be referenced by var.service_account_role_arn_annotation_enabled.

  description = <<-EOT
  Whether or not to dynamically insert an `eks.amazonaws.com/role-arn` annotation into `${var.service_account_set_key_path}.annotations`
  (by default, `serviceAccount.annotations`), with the value being the ARN of the IAM role created when `var.iam_role_enabled`.
  
  Assuming the Helm Chart follows the standard convention of rendering ServiceAccount annotations in `serviceAccount.annotations`
  (or a similar convention, which can be achieved by overriding `var.service_account_set_key_path` as needed),
  this allows the ServiceAccount created by the Helm Chart to assume the IAM Role in question via the EKS OIDC IdP, without
  the consumer of this module having to set this annotation via `var.values` or `var.set`, which would involve manually
  rendering the IAM Role ARN beforehand.
  
  Ignored if `var.iam_role_enabled` is `false`.
  EOT

This Pull Request has been updated, so we're dismissing all reviews.

This Pull Request has been updated, so we're dismissing all reviews.