feat: Update Terraform module versions to latest

[bryantbiggs]

Description

• Starting in v5.4 of the ECS module, enabling ECS exec is just a boolean flag without any additional changes required by users feat: Add support for easily enabling ECS Exec support terraform-aws-modules/terraform-aws-ecs#127
• The container definition port mapping name and hostPort values are not required so they have been removed
• The standard module definition requirements have been removed from the pre-commit checks - this is to de-emphasize modules here which also means we can remove the empty variables.tf files
• Updated and aligned the minimum supported versions of Terraform and the AWS provider to 1.0 and 5.0 respectively
• The Codepipeline/Codebuild/Codedeploy resources have been moved to their own codepipeline.tf file
• The module names and configurations have been updated to be consistent throughout the patterns
• Update queue processing example to use modules and align with the other patterns
• Replace use of shared Task exec role with service level Tasks exec role. For example - this is incorrect because the secret and SSM param ARNs are passed to the module to scope the Task exec policy to allow access to those values but its only valid if the service creates the service specific Task exec role. The use of the shared role means that potentially other tasks are accessing secrets/SSM params that they should not have access to

Motivation and Context

• There have been a number of significant updates to the modules and this takes advantage of those improvements
• Ensure the patterns are consistent and aligned with respect to the conventions used

How Has This Been Tested?

• 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

I've tested and validated the following:

• ec2-examples/
  • core-infra/
  • backend-service/
  • lb-service
• fargate-examples/
  • core-infra/
  • backend-service/
  • lb-service