[AWS::EC2::PrefixList] - [BUG] - Tags are not applied to existing resources on update

### Name of the resource

AWS::EC2::PrefixList

### Resource Name

_No response_

### Issue Description

If an existing `AWS::EC2::PrefixList` resource has `Tags` added, those are not applied to the resource. Nor are the CloudFormation default tags propagated to the resource.

Creating a new stack with a new PrefixList works as expected.

### Expected Behavior

1. Have an existing `AWS::EC2::PrefixList` resource, created before tags support was added.
2. Add `Tags` to the resource in your template.
3. Update stack.
4. Tags are applied to the resource, ideally together with CloudFormation's default tags.

### Observed Behavior

1. Have an existing `AWS::EC2::PrefixList` resource, created before tags support was added.
2. Add `Tags` to the resource in your template.
3. Update stack.
4. Tags are still empty on the resource.

### Test Cases

See Expected behaviour.

### Other Details

_No response_

No files, tests, or entry points are named. Start by tracing the AWS::EC2::PrefixList update path and reproduce the reported case: add Tags to an existing resource and update the stack. Done means both template tags and CloudFormation default tags are applied to the existing PrefixList, as they are for a new one.

Written by the indexing model from the issue text.