fix: Pin aws provider version prior to 5.x

[snovikov]

Description

As mentioned in #349 some modules used in current version of the module (v3.28.0) are not compatible with latest aws-provider. To fix it we have to adjust module requirments.

Motivation and Context

• Fix CI - currently GitHub actions are reporting errors like this:

  Validation failed: .
  ╷
  │ Warning: Argument is deprecated
  │ 
  │   with module.vpc.aws_eip.nat,
  │   on .terraform/modules/vpc/main.tf line 10[68](https://github.com/terraform-aws-modules/terraform-aws-atlantis/actions/runs/5867579962/job/15908553795#step:4:72), in resource "aws_eip" "nat":
  │ 1068:   vpc = true
  │ 
  │ use domain attribute instead
  ╵
  ╷
  │ Error: Unsupported argument
  │ 
  │   on main.tf line 597, in data "aws_iam_policy_document" "ecs_task_access_secrets_with_kms":
  │  597:   source_json = data.aws_iam_policy_document.ecs_task_access_secrets.json
  │ 
  │ An argument named "source_json" is not expected here.
  ╵

  Ref: https://github.com/terraform-aws-modules/terraform-aws-atlantis/actions/runs/5867579962/job/15908553795

Breaking Changes

• There is no breaking changes, but this change will prevent any further updated of aws provider v5.0+

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

[snovikov]

This could be a minor update -> e.g. v3.29.0 release.

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