[AWS::CodePipeline::Pipeline] - [BUG] - resource don't receive the aws:cloudformation built-in tags / default service-managed auto-tags

### Name of the resource

AWS::CodePipeline::Pipeline

### Resource Name

_No response_

### Issue Description

To find the right CloudFormation Stack, where a AWS resource is defined/maintained **aws:cloudformation:*** built-in tags are needed. This is an important function in day-to-day business.

### Expected Behavior

Resources with type `AWS::CodePipeline::Pipeline`, which are managed as CloudFormations Stacks, should automatically receive the `aws:cloudformation:*` built-in tags / automatic default CFN AutoTags.

Once support CloudFormation Drift-Detection will be added via https://github.com/aws-cloudformation/cloudformation-coverage-roadmap/issues/1909, please handled by those automatic tags correctly (hence, aws:cloudformation:* tags are _not_ a drift)

### Observed Behavior

When you have an `AWS::CodePipeline::Pipeline` resource in your stack, it does not get the built-in tags assigned: `aws:cloudformation:stack-name`, `aws:cloudformation:logical-id` and `aws:cloudformation:stack-id`

### Test Cases

Deploy a CloudFormation stack containing this resource named above (e.g. sample from AWS docs) and check the tags on the console. You can't see aws:cloudformation:* built-in tags (which should be added by CFN automatically).

### Other Details

_No response_

Deploy a CloudFormation stack containing an AWS::CodePipeline::Pipeline resource, using a sample from the AWS documentation, and inspect its tags in the console. Confirm that aws:cloudformation:stack-name, aws:cloudformation:logical-id, and aws:cloudformation:stack-id are present; the issue is done when these built-in tags are assigned automatically.

Written by the indexing model from the issue text.