Add IMDSv2 support

The template is older and does not take into account IMDSv2

The following needs to be updated

~line 447
`TOKEN=`curl -X PUT "http://169.254.169.254/latest/api/token" -H "X-aws-ec2-metadata-token-ttl-seconds: 21600"`
region=`curl -H "X-aws-ec2-metadata-token: $TOKEN" --silent http://169.254.169.254/latest/dynamic/instance-identity/document | grep region | cut -f 4 -d '"'`instanceId=`curl -H "X-aws-ec2-metadata-token: $TOKEN" --silent http://169.254.169.254/latest/meta-data/instance-id``

and line ~628
`TOKEN=`curl -X PUT "http://169.254.169.254/latest/api/token" -H "X-aws-ec2-metadata-token-ttl-seconds: 21600"`
aws ec2 associate-address --region ${AWS::Region} --instance-id $(curl -H "X-aws-ec2-metadata-token: $TOKEN" -s http://169.254.169.254/latest/meta-data/instance-id) --allocation-id $freeEIP --allow-reassociation || error_exit 'Failed to Associate Elastic IP'`

Open the template and inspect the shell commands around lines 447 and 628. Verify both instance-metadata lookups use the IMDSv2 token flow shown in the issue, then validate that the template still retrieves the region and instance ID and associates the Elastic IP successfully.

Written by the indexing model from the issue text.