feat: Allow setting additional role arns to trust policy in iam-role-for-service-accounts-eks

[ottramst]

Description

This changes allows the user to pass role ARN's into the iam-role-for-service-accounts-eks module for allowing additional IAM roles to assume the created role.

Motivation and Context

This change helps to facilitate some more complex setups in EKS where other roles need to access the IRSA enabled role.

For example: Keda autoscaler with pod identity authentication, where the Keda operator Pod (with IRSA enabled) will access the target (ScaledObject) Pod's attached role.

Breaking Changes

None

How Has This Been Tested?

• [x] I have updated at least one of the examples/* to demonstrate and validate my change(s)
• [x] I have tested and validated these changes using one or more of the provided examples/* projects
• [x] I have executed pre-commit run -a on my pull request

[github-actions[bot]]

This PR has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this PR will be closed in 10 days

[github-actions[bot]]

This PR was automatically closed because of stale in 10 days

[github-actions[bot]]

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.