Setting PropagateTagsToVolumeOnCreation results in a drift detection

### Name of the resource

AWS::EC2::Instance

### Resource Name

_No response_

### Issue Description

If the `PropagateTagsToVolumeOnCreation` property is set on the `AWS::EC2::Instance` resource type it will result in a drift detection for the resource. This appears to be caused by the actual state of the resource omitting `PropagateTagsToVolumeOnCreation`.

### Expected Behavior

There should not be a drift detection result for each EC2 instance resource which sets the `PropagateTagsToVolumeOnCreation` property when the property is unchanged.

### Observed Behavior

A drift detection result occurs for each EC2 instance resource which sets the `PropagateTagsToVolumeOnCreation` property.

### Test Cases

Create a CloudFormation stack with at least one `AWS::EC2::Instance` resource with the `PropagateTagsToVolumeOnCreation` property set to `true`. Once the stack has been created, initiate drift detection. The EC2 instance will be listed as drifted, and inspection of the resource state will show the actual state omits the `PropagateTagsToVolumeOnCreation` property.

### Other Details

_No response_

Start with the AWS::EC2::Instance resource and the PropagateTagsToVolumeOnCreation property. Reproduce the issue by creating a CloudFormation stack with the property set to true, then initiate drift detection and inspect the resource state. Done means an unchanged EC2 instance is no longer reported as drifted because of this property.

Written by the indexing model from the issue text.