default http-put-response-hop-limit to 1 for al2023

[Issacwww]

Issue #, if available:

Description of changes:
this option is default to 2, per this doc.
And suggested by AppSec, since we supported pod identity, we should default it to 1

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Testing Done
Build 1.28 AMI and tested with kubetest2 and conformance

See this guide for recommended testing for PRs. Some tests may not apply. Completing tests and providing additional validation steps are not required, but it is recommended and may reduce review time and time to merge.

[cartermckinnon]

Do the metadata_options apply to Packer's builder instance, to the resulting AMI, or both?

My understanding is the http_tokens bit only applied to the builder instance. What does this hop limit apply to?

[Issacwww]

Do the metadata_options apply to Packer's builder instance, to the resulting AMI, or both?
Ah, you are right, this is for packer builder instance, we still need config the resulting AMI

[Issacwww]

Discard this change as the IMDS Hop should be set when launch ec2 instance, thus need change this config in our launch template. This should be set for MNG, for self MNG cx should set it to 1 in their own LT