[TF-10414] Replace EC2 AWS Launch Configuration for AWS Launch Templates

[miguelhrocha]

Background

Working on the AWS TFE FDO Standalone Mounted Disk, I've realized that to have a successful automated upgrade, we have to enable EBS volume creation from snapshot_ids.

While enabling that, I've found that the creation of a new EC2 launch configuration will be deprecated by EOY, in favor of EC2 Launch templates.

It adds the following arguments to the root module:

1. An optional ebs_snapshot_id argument, so mounted disk installations can be instantiated from an EBS snapshot
2. An optional list of ec2_launch_template_tag_specifications, so components created by the Launch configuration can be tagged accordingly.

Relates OR Closes #316

How Has This Been Tested

1. Via the standalone mounted disk module test
2. Locally using a custom terraform module that uses the new arguments

[miguelhrocha]

/test standalone-vault destroy=true

✅ Terraform AWS Standalone Vault (FDO) - Test Report

🔗 Action Summary Page

• ✅ Terraform Init

• ✅ Terraform Validate

• ✅ Terraform Apply

• ✅ Run k6 Smoke Test

• ✅ Terraform Destroy

[anniehedgpeth]

/test public-active-active-replicated

✅ Terraform AWS Public Active/Active (Legacy) - Test Report

🔗 Action Summary Page

• ✅ Terraform Init

• ✅ Terraform Validate

• ✅ Terraform Apply

• ✅ Run k6 Smoke Test

• ✅ Terraform Destroy

[anniehedgpeth]

⭐ Thanks for the improvement!