Maintenance: add subpath exports to package.json

[am29d]

Summary

We currently don't export subpaths for envelopes, schemas and types in our package.json, and we should add them, so customers can import them.

Why is this needed?

So customers can granularly import schemas and envelopes following the same standard that we have introduced with in v2.

Which area does this relate to?

No response

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.