JENKINS-71655: Add support for AMIs without instance metadata support

[nagrubb]

After https://issues.jenkins.io/browse/JENKINS-65127 was introduced with #609, AMIs without Instance Metadata support were broken. When they were provisioned, they wouldn't get key pairs properly installed by AWS EC2 (the init script on the AMIs would get stuck on waiting to access instance-metadata).

This change introduces a new option to indicate if an AMI does not support instance metadata and thus no InstanceMetadataOptionsRequest will be included in the EC2 request to provision an instance.

Testing done

• Introduced a new automated test SlaveTemplateTest.provisionOnDemandWithUnsupportedInstanceMetadata()
• Ran mvn test to make sure no other tests were broken.
• Ran mvn hpi:run to make sure the UI showed the new option for metadata supported.

Submitter checklist

Preview Give feedback

1. Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
2. Ensure that the pull request title represents the desired changelog entry
3. Please describe what you did
4. Link to relevant issues in GitHub or Jira
5. Link to relevant pull requests, esp. upstream and downstream changes
6. Ensure you have provided tests - that demonstrates feature works or fixes the issue

[nagrubb]

@warrior8792 @res0nance Could you help to review this please?

[nagrubb]

Thank you!