chore: Start V2 branch (#1346)

* Initial commit

* Add warning

Author: scottgerring

README.md

@@ -1,4 +1,6 @@
-# Powertools for AWS Lambda (Java)
+# Powertools for AWS Lambda (Java) V2
+
+**This is pre-release code for Powertools for AWS Lambda (Java) V2! Please check out the `main` branch for the stable release** 
 
 ![aws provider](https://img.shields.io/badge/provider-AWS-orange?logo=amazon-aws&color=ff9900) ![Build status](https://github.com/aws-powertools/powertools-lambda-java/actions/workflows/build.yml/badge.svg) ![Maven Central](https://img.shields.io/maven-central/v/software.amazon.lambda/powertools-parent) [![codecov.io](https://codecov.io/github/aws-powertools/powertools-lambda-java/branch/main/graphs/badge.svg)](https://app.codecov.io/gh/aws-powertools/powertools-lambda-java)
 

docs/utilities/large_messages.md

@@ -6,12 +6,6 @@ description: Utility
 The large message utility handles SQS and SNS messages which have had their payloads
 offloaded to S3 if they are larger than the maximum allowed size (256 KB).
 
-!!! Notice
-    The large message utility (available in the `powertools-sqs` module for versions v1.16.1 and earlier) is now deprecated
-    and replaced by the `powertools-large-messages` described in this page.
-    You can still get the documentation [here](sqs_large_message_handling.md)
-    and the migration guide [here](#migration-from-the-sqs-large-message-utility).
-
 ## Features
 
 - Automatically retrieve the content of S3 objects when SQS or SNS messages have been offloaded to S3.

docs/utilities/sqs_batch.md

@@ -35,7 +35,6 @@
         <module>powertools-examples-idempotency</module>
         <module>powertools-examples-parameters</module>
         <module>powertools-examples-serialization</module>
-        <module>powertools-examples-sqs</module>
         <module>powertools-examples-batch</module>
         <module>powertools-examples-validation</module>
         <module>powertools-examples-cloudformation</module>