Support configurable aws-auth-config-map in deploy/infrastructure

[StevenPG]

Is your feature request related to a problem? Please describe.

When deploying the dss using a service account through automation, only that service account has access to the cluster as well as terraform and helm access.

This limits the team's ability to perform upgrades and debug issues within the cluster without configuring the automation to execute an altered tf script from within deploy/operations (kubernetes_admin_access.tf)

New organizations attempting to utilize the DSS would have an easier time deploying if they can provide their standard EKS configuration in the terraform.

Describe the solution you'd like

A configurable way to provide the aws-auth-config-map in the deploy/infrastructure terraform configuration within the tf configuration such that a team can be provisioned access automatically on creation of the cluster.

This is currently available for the cluster creator to create using the deploy/operations scripts, but the config-map must be altered. It would be ideal for this to live in the terraform config in the personal folder so that the repository stays clear of changes, but a team can be provisioned access in one terraform execution.

Describe alternatives you've considered

Our team has manually shared the terraform state and manually executed the kuberetes_admin_access.tf with changes to the aws-auth-config-map content.