patch(deps): update terraform aws to v5.23.1

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
aws (source)	required_provider	patch	5.23.0 -> 5.23.1

---

Release Notes

hashicorp/terraform-provider-aws (aws)

v5.23.1

Compare Source

BUG FIXES:

• data-source/aws_lambda_function: Add vpc_config.ipv6_allowed_for_dual_stack attribute, fixing Invalid address to set: []string{"vpc_config", "0", "ipv6_allowed_for_dual_stack"} errors (#​34134)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[github-actions]

Terraform Format success

Output

Terraform Init success

Output

Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- Installing hashicorp/aws v5.23.1...
- Installed hashicorp/aws v5.23.1 (signed by HashiCorp)
- Installing cloudflare/cloudflare v4.17.0...
- Installed cloudflare/cloudflare v4.17.0 (self-signed, key ID C76001609EE3B136)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html

Terraform has made some changes to the provider dependency selections recorded
in the .terraform.lock.hcl file. Review those changes and commit them to your
version control system if they represent changes you intended to make.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Terraform Validation success

Output

Success! The configuration is valid.

Terraform Plan success

Output

cloudflare_zone.gopad: Refreshing state... [id=af26f110aba5bd79176147dc3dbc3511]
cloudflare_record.github: Refreshing state... [id=98c891e20c496c4fd8d2f0adc16d58d1]
cloudflare_record.root: Refreshing state... [id=a4df1bd2e41ab73009055cae03420e1f]
cloudflare_record.www: Refreshing state... [id=415e93d3c92e25bf9e5019b9ffe1e067]
aws_s3_bucket.download: Refreshing state... [id=dl.gopad.eu]
aws_s3_bucket_website_configuration.download: Refreshing state... [id=dl.gopad.eu]
aws_s3_object.download: Refreshing state... [id=index.html]
aws_s3_bucket_policy.download: Refreshing state... [id=dl.gopad.eu]
aws_s3_bucket_acl.download: Refreshing state... [id=dl.gopad.eu,public-read]
aws_s3_bucket_cors_configuration.download: Refreshing state... [id=dl.gopad.eu]
cloudflare_record.download: Refreshing state... [id=8c7a6c57f61f27e1d8ac8822448dbd65]

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

Pusher: @renovate[bot], Action: pull_request