Maintenance: Preparation for V2

[scottgerring]

Summary

To shift our focus to V2, we need some more basic plumbing set up first in the V2 branch, before we can start accepting contributions

• Remove deprecated modules code now - to make future merges down from main simpler
• Enable branch protection for v2
• Setup build rules to run on v2 as if it were main
• Banner / statement about continued support for v1 (delay until we have an RC probably?)

Why is this needed?

So that we can begin to accept V2 work, easily and robustly, as we accept work for V1/main.

Which area does this relate to?

No response

Solution

No response

Acknowledgment

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

[scottgerring]

I will try and sort this out this week in an effort to unblock V2 contributions. Please add anything else you see being necessary here @jeromevdl / @msailes / @mriccia

[scottgerring]

Done. v2 branch has been recreated from main, and deprecated modules have been removed. We've also setup the build jobs to run for the branch, and branch protection, the same as main.