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

The issue concerns AWS Lambda layers and unique tags at the layer-version level, but names no repository files, tests, or implementation entry point. Start by checking the AWS Lambda tagging APIs and the project's layer-version handling. Done means layer versions support distinct tags for organization, cost allocation, ownership, and automation.

Written by the indexing model from the issue text.