AWS::CertificateManager::Certificate doesn't remove created DNS validation CNAME on delete

### Name of the resource

Other

### Resource Name

AWS::CertificateManager::Certificate

### Issue Description

The AWS::CertificateManager::Certificate resource can create a validation CNAME in a Route 53 hosted zone as part of the certificate provisioning process. However when deleted it does not remove created record(s) it created, which can lead to a deletion failure of the AWS::Route53::HostedZone resource due to the presence of additional records.

### Expected Behavior

AWS::CertificateManager::Certificate should remove up any Route53 entries it creates unless DeletionPolicy: Retain is specified.

### Observed Behavior

Deletion of an AWS::CertificateManager::Certificate resource, with no explict DeletionPolicy removes the certificate itself from ACM, but does not remove the associated CNAME validation record it created in Route53.

### Test Cases

* Verify that deletion of a stack containing an AWS::CertificateManager::Certificate resource with DeletionPolicy: Retain does NOT delete either the certificate or it's associated validation CNAME
* Verify that deletion of a stack containing an AWS::CertificateManager::Certificate resource with no explicit deletion policy DOES delete BOTH the certificate and the validate CNAME created by the resource
* Verify that deletion of a stack containing an AWS::CertificateManager::Certificate resource with DeletionPolicy: DeleteDOES delete BOTH the certificate and the validate CNAME created by the resource

### Other Details

_No response_

Start with the AWS::CertificateManager::Certificate deletion behavior and the issue's Test Cases, focusing on the Route 53 validation CNAME and the stack's DeletionPolicy. Done means confirming that default and Delete policies remove both the certificate and created CNAME, while Retain removes neither.

Written by the indexing model from the issue text.