feat: Allow task exec IAM policy to have an IAM path

[rmolson]

Description

This PR adds the ability to have a path in the task exec policy in modules/service/main.tf

Motivation and Context

On some of the accounts I work on, I can't write a role or policy to the root of IAM, I have to put each policy in a different IAM path based on different factors. While most of the policies support this, there is one that is missing the path argument.

Also noted in #199

Breaking Changes

No breaking changes

How Has This Been Tested?

• I have updated at least one of the examples/* to demonstrate and validate my change(s)
• I have tested and validated these changes using one or more of the provided examples/* projects

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

[rmolson]

$terraform version
Terraform v1.10.0
on linux_amd64
+ provider registry.terraform.io/hashicorp/aws v5.78.0

$pre-commit run -a
Terraform fmt............................................................Passed
Terraform wrapper with for_each in module................................Passed
Terraform docs...........................................................Passed
Terraform validate with tflint...........................................Passed
Terraform validate.......................................................Passed
check for merge conflicts................................................Passed
fix end of files.........................................................Passed
trim trailing whitespace.................................................Passed

Trying to figure what the difference is in the pipeline. for the document updates, I think the pipeline is using 1.9, should lower my terraform version locally to 1.9.x?

Updated, updated my local terraform-docs

[rmolson]

This now passes on actions on my fork, please approve the workflow again.

[antonbabenko]

This PR is included in version 5.12.0 🎉

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