Maintenance: add JMESPath package to workspace

[dreamorosi]

Summary

Over the past few months we have been working on a new JMESPath utility. These efforts have been going on under the feat/jmespath branch, which has now become too big to review.

We are going to break down the branch into smaller PRs, and as a first step we should create the necessary folder structure for the new utility to exist in the monorepo.

Why is this needed?

So that we can make the package part of the workspace.

Which area does this relate to?

JMESPath

Solution

No response

Acknowledgment

• This request meets Powertools for AWS Lambda (TypeScript) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.