feat: Added variable trusted_role_actions to sub modules as a "Action of STS"

[tcharewicz]

Description

Orginaly I create issue with "Adding variable trusted_role_actions to other sub-modules"
- iam-assumable-roles
- iam-assumable-role-with-saml
- iam-assumable-roles-with-saml

• Resolves Feat: Adding variable trusted_role_actions to other sub-modules #392

At the time of PR creation I found that, in sub module iam-assumable-role-with-saml this variable is used, but in different way comparing to sub module iam-assumable-role.

In module with iam-assumable-role-with-saml is used as a "Extra Actions of STS"

variable "trusted_role_actions" {
  description = "Extra Actions of STS"
  type        = list(string)
  default     = [""]
}

In module with iam-assumable-role is used as a "Actions of STS"

variable "trusted_role_actions" {
  description = "Actions of STS"
  type        = list(string)
  default     = ["sts:AssumeRole"]
}

That way finally PR is adding this variable as a "Extra Actions of STS" to sub modules:

• iam-assumable-role
• iam-assumable-roles
• iam-assumable-roles-with-saml

Motivation and Context

It's useful to use two additional action with STS action:

sts:SetSourceIdentity
sts:TagSession

But when you want to use them, you need to add them to all roles in AWS Account.

Breaking Changes

None, all orginal default action are preserved.

How Has This Been Tested?

• [yes] I have executed pre-commit run -a on my pull request

[antonbabenko]

This PR is included in version 5.23.0 🎉

[tcharewicz]

@bryantbiggs Thx.

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