AWS::ElasticLoadBalancingV2::TargetGroup resources don’t receive the aws:cloudformation built-in tags / default AutoTags

### Name of the resource

AWS::ElasticLoadBalancingV2::TargetGroup

### 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

All stack resources of type `AWS::ElasticLoadBalancingV2::TargetGroup` 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::ElasticLoadBalancingV2::TargetGroup` resource in your stack, it does not get assigned the built-in tags: `aws:cloudformation:stack-name`, `aws:cloudformation:logical-id` and `aws:cloudformation:stack-id`

### Test Cases

deploy a 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.

### Other Details

split from https://github.com/aws-cloudformation/cloudformation-coverage-roadmap/issues/458#issuecomment-627907661 for better viewability

Start by deploying a stack containing an AWS::ElasticLoadBalancingV2::TargetGroup, using a sample from the AWS docs, and inspect its tags in the console. The work is done when the resource receives the aws:cloudformation:stack-name, logical-id, and stack-id tags and CloudFormation Drift Detection does not report those tags as drift.

Written by the indexing model from the issue text.