Let AWS Lambda SQS handlers report partial batch failures

[laurit]

Resolves #14441

Reporting partial batch failures requires using SQSBatchResponse which is not available in 2.2 that we currently have library instrumentation for. This PR adds a new library instrumentation for 3.11. This is unusual since for other instrumentations we don't have library instrumentations for multiple versions. I'm looking for feedback on how we should handle this. Keep javaagent at 2.2 and move library to 3.11? If we are going to do that then changing the package name is going to break existing code, is that fine or should we do some sort of deprecation cycle? If we are going to remove the 2.2 module should we try to do maven relocation to new coordinates (have we done this before)? cc @trask
Bumping the library version would also unblock #8642

[trask]

I like the idea of a deprecation cycle for the 2.2 library module where we mark all the public classes as deprecated

I'd suggest keeping the Java agent instrumentation at 2.2 to stay consistent with https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/VERSIONING.md#dropping-support-for-older-library-versions

[laurit]

I like the idea of a deprecation cycle for the 2.2 library module where we mark all the public classes as deprecated

I think the only open question would be whether we introduce a new module that is shared between the deprecate 2.2 and 3.1 or move all shared internal classes to 3.1 and make 2.2 depend on 3.1. Perhaps the common module would be better since we could keep compiling it against 2.2 and agent could depend on it instead of the new 3.1 module.

I'd suggest keeping the Java agent instrumentation at 2.2 to stay consistent with https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/VERSIONING.md#dropping-support-for-older-library-versions

This shouldn't be a problem since the agent only uses internal classes from the library module which didn't change.

[trask]

👍