### Why is this needed? There are a few areas left from v1 to v2 we couldn't optimize, namely for now are: * [x] #2204 * [x] #2205 * [x] #2206 * [x] #2207 * [x] #2208 * [x] #2209 * [x] #2210 * [x] #2211 * [x] #2212 * [x] #2213 * [x] Add documentation at the top of workflows as complexity is growing * [x] Convert reusable workflows to composite actions * [x] Use `format` built-in function to use constants for hashing folders * [x] Create visual representation of release process as per @leandrodamascena ask ### Which area does this relate to? Other ### Suggestion _No response_ ### Acknowledgment - [X] This request meets [Lambda Powertools Tenets](https://awslabs.github.io/aws-lambda-powertools-python/latest/#tenets) - [X] Should this be considered in other Lambda Powertools languages? i.e. [Java](https://github.com/awslabs/aws-lambda-powertools-java/), [TypeScript](https://github.com/awslabs/aws-lambda-powertools-typescript/), and [.NET](https://github.com/awslabs/aws-lambda-powertools-dotnet/)
Why is this needed?
There are a few areas left from v1 to v2 we couldn't optimize, namely for now are:
formatbuilt-in function to use constants for hashing foldersWhich area does this relate to?
Other
Suggestion
No response
Acknowledgment