[ECS] [Fargate] [Feature Request]: ECS Fargate tasks to support aws:cloudformation:stack-name tag to be propagated automatically

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
What do you want us to build?
ECS Fargate tasks to support aws:cloudformation:stack-name tag to be propagated automatically

**Which service(s) is this request for?**
Fargate, ECS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Problem Statement: 
The aws:cloudformation:stack-name tag is used as a cost allocation tag to track costs associated with various AWS resources, including those launched by CloudFormation stacks.
However, ECS Fargate does not currently support automatic propagation of this tag to its tasks, making it difficult to accurately track Fargate-related costs per CloudFormation stack.

Impact:
Most other AWS resources support the propagation of the aws:cloudformation:stack-name tag, but its absence in ECS Fargate introduces additional complexity in cost tracking. This requires manual creation of custom cost allocation tags with the same value, which adds overhead to the process of merging cost data across resources.

Request:
It would be highly beneficial to prioritise the implementation of this feature, aligning ECS Fargate with the tag propagation behaviour of other services and improving cost visibility and reporting across environments.

**Are you currently working around this issue?**
How are you currently solving this problem?
A custom cost allocation tag with the same value as the aws:cloudformation:stack-name can be used as a temporary solution, though it adds complexity to cost management.

**Additional context**
Anything else we should know?

**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)