[AWS::ECS::TaskDefinition] - [BUG] - resources don't receive the aws:cloudformation built-in tags / default service-managed auto-tags

### Name of the resource

AWS::ECS::TaskDefinition

### 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::ECS::TaskDefinition`, which are managed as CloudFormations Stacks, should automatically receive the `aws:cloudformation:*` built-in tags / automatic default CFN AutoTags.

Furthermore those aws:cloudformation:* built-in tags must be handled by CloudFormation Drift-Detection correctly (hence, aws:cloudformation:* tags are _not_ a drift)

### Observed Behavior

When you have an `AWS::ECS::TaskDefinition` 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.

I've re-tested it right now in eu-central-1 region. No tags `aws:cloudformation:*` are added to the ECS TaskDefinition resource.

### Other Details

In the area of AWS Elastic Container Service the resource AWS::ECS::Cluster already receiving aws:cloudformation:* auto-tags. Furthermore, the previous issue https://github.com/aws-cloudformation/cloudformation-coverage-roadmap/issues/1521 got closed by a mistake of cfn-github-issues-bot.

Deploy a CloudFormation stack containing an AWS::ECS::TaskDefinition, using a sample from the AWS documentation, and inspect its tags in the console in a region such as eu-central-1. Compare the result with AWS::ECS::Cluster and verify whether the aws:cloudformation:* tags appear and are excluded from CloudFormation drift detection.

Written by the indexing model from the issue text.