[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.

El issue se refiere a AWS Lambda layers y a tags únicos en el nivel de layer-version, pero no indica archivos del repositorio, pruebas ni un punto de entrada de implementación. Empieza comprobando las AWS Lambda tagging APIs y el manejo de layer-version del proyecto. Se considera terminado cuando las layer versions admiten tags distintos para organización, asignación de costes, propiedad y automatización.

Escrito por el modelo de indexación a partir del texto del issue.