[Lambda] Layer: Add Tags Support

### 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**
Enable tagging for Lambda layers, with support for unique tags at the layer version level. Tags could be used for cost allocation, resource organization, automation purposes, ownership identifications.

**Which service(s) is this request for?**
AWS Lambda

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Currently, Lambda layers do not support tagging, which limits the ability to organize and manage layers effectively. Tags are essential for tracking costs, associating layers with specific applications, and automating resource management. This is especially true if all lambdas using this layer have been deleted.

L’issue concerne les AWS Lambda layers et les tags uniques au niveau de layer-version, mais ne nomme aucun fichier du dépôt, test ou point d’entrée de l’implémentation. Commencez par vérifier les AWS Lambda tagging APIs et la gestion de layer-version du projet. La tâche est terminée lorsque les layer versions prennent en charge des tags distincts pour l’organisation, l’allocation des coûts, la responsabilité et l’automatisation.

Rédigé par le modèle d'indexation à partir du texte de l'issue.