changes launch configuration to launch template

[acsrujan]

No description provided.

[hashicorp-cla]

All committers have signed the CLA.

[brikis98]

A couple worries:

1. This is a very backwards incompatible change... And I'm not seeing a migration path here other than "undeploy your entire cluser and redeploy based on launch templates." We'd need to think through how existing users would be able to upgrade without downtime.

2. Is there anything a launch config can do that a launch template can't? I know we gain some features with launch templates, but are we losing any?

[acsrujan]

Hey,

1. Yes. I left it in draft version for work in progress. I'll close it and raise one when it's ready with backward compatible version (if feasible).
   Upgrade without downtime is not yet addressed. I'm considering if we create launch template, attach it to existing ASG. Still working on making it frictionless.
   This might require a discussion here or Feature Request: Support Launch-Templates for t2/t3 unlimited configuration #103

2. No, both from official documentation and personal experience.