Optionally enforce IMDSv2 on kitchen instances.

[bobchaos]

Description

Provides an option to enforce IMDSv2 on kitchen instances.

I considered exposing metadata_options directly but this brings it in line with the way it's done in the AWS console.

Issues Resolved

#479

Check List

• All tests pass. See TESTING.md for details.
• New functionality includes testing.
• New functionality has been documented in the README if applicable.

[bdwyertech]

Blah, I just added support for similar -- I think we should expose metadata options as well, especially now that control of instance tags via metadata is also exposed via this config block.

https://aws.amazon.com/about-aws/whats-new/2022/01/instance-tags-amazon-ec2-instance-metadata-service/

[tas50]

@bobchaos can you rebase this and add the docs to https://github.com/test-kitchen/test-kitchen/blob/main/docs/content/docs/drivers/aws.md

[bdwyertech]

@bobchaos can you rebase this and add the docs to https://github.com/test-kitchen/test-kitchen/blob/main/docs/content/docs/drivers/aws.md

@tas50 the metadata addition would encompass this as well so you can prob close this out.

We need the whole block exposed because it is used to enable instance tags via metadata as well as the IMDSv2 hardening config.