Resolve warnings in deployments

[GaryGSC]

I'm treating this as a tracking issue.

Warnings about S3 resource deprecations in our Terraform plans:

• Use tfedit to stop directly using deprecated S3 resources #688
• Bump TF module versions #695
• Update terraform-aws-postman-test-lambda to v5.0.0 #716

Deprecation notices related to actions running on node12:

• fix: call echo to determine environment where credentials are valid github-action-start-standard-change#38
• Work with Tyk github-action-end-standard-change#22
• Run using Node.js 16, bump NPM & GHA deps github-action-tf-plan-analyzer#153
• Update dependencies, resolve external-facing deprecations github-action-tf-plan-comment#27
• Run using Node.js 16, bump NPM & GHA deps github-action-codedeploy#26 (via Use codedeploy action @v2 #715)
• Replace deprecated set-output function with GITHUB_OUTPUT aws-actions/configure-aws-credentials#521 (via Bump aws-actions/configure-aws-credentials from 1 to 2 #855)
  • They have a solution available: referencing @v1-node16. They say they'll keep it up to date. Will that play nicely with Dependabot when @v2 is eventually released? I'm not sure.

Deprecation notices related to set-output:

• Fix deprecated usage of set-output #681
• Run using Node.js 16, bump NPM & GHA deps github-action-tf-plan-analyzer#153
• Update dependencies, resolve external-facing deprecations github-action-tf-plan-comment#27
• Run using Node.js 16, bump NPM & GHA deps github-action-codedeploy#26 (via Use codedeploy action @v2 #715)
• Bump deps, fix set-output deprecation github-action-start-standard-change#40
• Replace deprecated set-output function with GITHUB_OUTPUT aws-actions/configure-aws-credentials#521 (via Bump aws-actions/configure-aws-credentials from 1 to 2 #855)
• set-output deprecation hadolint/hadolint-action#63 (via Bump hadolint/hadolint-action from 2.1.0 to 3.0.0 #729)

DivvyCloud warnings:

• Resolve DivvyCloud warnings in Terraform plan #104 (blocked)
  • We could move to the new official DivvyCloud action, but we'd probably have the same issue with a worse UI
  • We could move to tfsec instead of DivvyCloud as suggested here, but that comes with it's own can of worms.

[GaryGSC]

#104 already has its own issue and everything else in this list has been resolved.