### Why is this needed? Our CI times doubled as GH has a limit of concurrent workflows run, increasing our lead time. ### Which area does this relate to? _No response_ ### Solution Short-term: change `paths` in Pydantic V2 workflow to only use Event Handler, Parser, and Batch. Medium-term: if CI time continues to be high, we use `nox` like solution to dynamically swap Pydantic version at runtime (no additional workflow). Long-term: Launch v3 with Pydantic v2 and drop v1. ### Acknowledgment - [X] This request meets [Powertools for AWS Lambda (Python) Tenets](https://docs.powertools.aws.dev/lambda/python/latest/#tenets) - [ ] Should this be considered in other Powertools for AWS Lambda languages? i.e. [Java](https://github.com/aws-powertools/powertools-lambda-java/), [TypeScript](https://github.com/aws-powertools/powertools-lambda-typescript/), and [.NET](https://github.com/aws-powertools/powertools-lambda-dotnet/)