CloudFormation stack does not automatically release mac1.metal host resource after stack deletion

### Name of the resource

AWS::CloudFormation::Stack

### Resource Name

_No response_

### Issue Description

If using cloudformation stack to create a aws::ec2::host resource with instancetype mac1.metal, this host is not automatically released after stack deletion (until user manually releases). Note that the stack is deleted after 24 hours, as to not be affected by the locked period for mac hosts. This does not occur with any other instances types on hosts, such as r5.large.

### Expected Behavior

mac1.metal host automatically released after stack deletion after some time (scrubbing workflow delays possibly)

### Observed Behavior

mac1.metal host is not automatically released after stack deletion (until user manually releases)

### Test Cases

create stack with aws::ec2::host resource with instance type mac1.metal, and aws::ec2::instance to be launched on this host. After 24 hours from stack creation, delete stack, observe host is not automatically released

### Other Details

_No response_

Reproduce the reported scenario with an AWS::CloudFormation::Stack containing an AWS::EC2::Host using mac1.metal and an instance launched on that host. Delete the stack after 24 hours and verify whether the host is released automatically; completion means the host is released without manual intervention.

Written by the indexing model from the issue text.