Publish to Elastic Beanstalk should expose IMDSv1 parameter

IMDSv1 has been superseded by IMDSv2 and AWS is suggesting to upgrade to it everywhere, since IMDSv2 is inherently more secure. I noticed that when publishing applications with AWS Toolkit to Elastic Beanstalk, the EC2 instances have the IMDSv1 property activated.

Deploying a workload with a possible insecure setting should be avoided whenever possible, especially for a tool such as AWS Toolkit that is thought hide complexities and details that aren't needed for a developer that is approaching to AWS for the first time. For this reason I suggest to set IMDSv1 as disabled by default and expose the parameter in the configuration in the publish wizard.

Optionally, I would also add a link to AWS documentation that explains what IMDS is in general and why IMDSv1 should be disabled.

Start by tracing the Elastic Beanstalk publish wizard and how it configures EC2 instance metadata settings, then consult the AWS documentation on IMDSv1 and IMDSv2. Done means IMDSv1 is disabled by default, the publish configuration exposes the parameter, and the proposed explanatory documentation link is included if supported.

Written by the indexing model from the issue text.