[IBCDPE-1005] eks developer role

[BryanFauble]

Problem:

1. As a user with a Developer level role I do not have access to the EKS cluster in any way.

Solution:

1. Creating an access entry for both Administrator and Developer SSO roles that have an EKS policy to access resources on the cluster
2. This gives cluster level read access: https://docs.aws.amazon.com/eks/latest/userguide/access-policies.html

Testing:

1. I updated my kube config and verified I could access resources from both sso roles
2. I tested that I was able to view all resources and perform port-forwarding sessions
   

[thomasyu888]

🔥 LGTM! Going to pre-approve - not sure if @BWMac had some comments!

[zaro0508]

i think this is the wrong approach, see my comments in PR Sage-Bionetworks-IT/organizations-infra#1191

[BryanFauble]

i think this is the wrong approach, see my comments in PR Sage-Bionetworks-IT/organizations-infra#1191

@zaro0508 You bring up an excellent point that I didn't think of until you brought this up.

I actually don't need to create a new role for one to assume in this case. What I can do instead is to add these existing assumed roles as an IAM access entry to the cluster. This prevents the need to assume another role with these permissions, and instead I can directly grant these permissions like:

I will update this PR accordingly

[BryanFauble]

Unfortunately this syntax was a bit complex, in part because:

1. data.aws_iam_roles.administrator-roles.arns is a set that needs to be converted to a list for some of these other functions to work
2. zipmap is used here to allow getting the index in the for loop
3. The index was added to the for loop in the event we were going to add multiple ARNs for each of these access entries the key would conflict if we didn't have a unique index

[thomasyu888]

Great changes and thanks for the review khai!