AWS::Logs::Delivery - BUG - different partitioning via s3SuffixPath during create and update for cloudfront sources

### Name of the resource

AWS::Logs::Delivery

### Resource Name

_No response_

### Issue Description

When viewing the configuration in the AWS Management Console for a CloudFront Distribution after creating an AWS::Logs::Delivery via CloudFormation, the partitioning has the form `AWSLogs/{account-id}/CloudFront/` .

When updating the S3SuffixPath, the partitioning shown in the AWS Management Console only shows the `` without the `AWSLog/{account-id}/CloudFront` prefix that was generated during creation, leading to inconsistent behavior between the creation and an update.

### Expected Behavior

Creation and updates behave the same, either with the `AWSLogs/{account-id}/CloudFront` prefix added or not (preferably without it).

### Observed Behavior

When creating an AWS::Logs::Delivery, the `AWSLogs/{account-id}/CloudFront` prefix is prepended to the S3SuffixPath. Subsequent updates remove the prefix again.

### Test Cases

Subsequent updates following the creation of an AWS::Logs::Delivery do not add or remove additional hierarchies in front of the S3SuffixPath.

### Other Details

_No response_

Start by reproducing an AWS::Logs::Delivery configuration for a CloudFront source, recording the S3SuffixPath shown after creation and after an update. Compare the AWS Management Console results; done means creation and subsequent updates use the same partitioning without adding or removing extra hierarchy.

Written by the indexing model from the issue text.