Upgrade packages to support AWS v4

[johncblandii]

what

• Upgraded outdated packages and versions.tf

why

• to support AWS v4 provider

references

• Closes Support AWS Provider v4, Support latest context.tf #75
• Closes Update Terraform cloudposse/s3-log-storage/aws to v0.28.0 - abandoned #62

[johncblandii]

/test all

[johncblandii]

/test all

[johncblandii]

🤷🏽

TestExamplesComplete/Enabled 2022-07-01T22:36:49Z command.go:121: module.s3_website.module.logs.module.aws_s3_bucket.aws_s3_bucket.default[0]: Creating...
TestExamplesComplete/Disabled 2022-07-01T22:36:49Z command.go:121: ""
    examples_complete_test.go:109: 
        	Error Trace:	examples_complete_test.go:109
        	Error:      	Should be empty, but was ""
        	Test:       	TestExamplesComplete/Disabled

https://github.com/cloudposse/actions/runs/7157658521?check_suite_focus=true#step:9:679

[nitrocode]

@johncblandii I believe this test fails because we're returning empty strings instead of null. I believe there was a discussion on it and we came to the conclusion that it's better to return an empty string.

The test probably needs to be updated because I think it's using an "exact search match" for the resource counts being zero.

terraform-aws-s3-website/test/src/examples_complete_test.go

Lines 108 to 109 in 106b3e5

	// Verify we're getting back the outputs we expect
	assert.Empty(t, s3BucketDomainName)

[johncblandii]

@johncblandii I believe this test fails because we're returning empty strings instead of null. I believe there was a discussion on it and we came to the conclusion that it's better to return an empty string.

The test probably needs to be updated because I think it's using an "exact search match" for the resource counts being zero.

terraform-aws-s3-website/test/src/examples_complete_test.go

Lines 108 to 109 in 106b3e5

	// Verify we're getting back the outputs we expect
	assert.Empty(t, s3BucketDomainName)

Makes sense. I'll update it later.

[arichtman]

Any chance we could get this moving again? I can take a crack at updating that test assertion?