Maintenance: create automation to publish v2 docs under `next` alias

[dreamorosi]

Summary

In #1717 we have created an automation that allows us to publish the content of the v2 branch to npmjs.com. As a continuation of that task we should extend that workflow to publish the documentation for that branch under the next alias whenever a pre-release is made.

Why is this needed?

So that customers can have documentation about the new features as soon as it's available.

Which area does this relate to?

Automation

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 ⚠️

Comments on closed issues 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.