Allow usage of depends_on for accelerator module, remove fargate_profiles from base example

[Zvikan]

What does this PR do?

• Create TF resource per IAM role policy attach for known policies
• Add depends_on for eks-cluster-with-new-vpc example between accelerator module and vpc
• Remove fargate_profiles from the example to allow GovCloud users to try the example.

Motivation

Cleaner TF destroy, avoid scenarios where VPC resources are deleted before EKS managed node groups does which leads to exceptions and the need of multiple destroy retries.

More

• Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
• Yes, I have added a new example under examples to support my PR
• Yes, I have created another PR for add-ons under add-ons repo (if applicable)
• Yes, I have updated the docs for this feature
• Yes, I ran pre-commit run -a with this PR

Note: Not all the PRs required examples and docs except a new pattern or add-on added.

For Moderators

• E2E Test successfully complete before merge?

Additional Notes

[vara-bonthu]

I understand this change is to avoid Error: Invalid for_each argument issue with module level dependency using aws.vpc.

PR looks good to me. Few changes needs to be done. Thanks 👍🏼

[vara-bonthu]

LGTM 👍🏼