Create BatchItemFailure structs for DynamoDB, Kinesis, SQS

[lyoung-confluent]

This change adds the response structs for "reporting batch item failures" documented in:

• DynamoDB: Reporting batch item failures
  
• Kinesis: Reporting batch item failures
  
• SQS: Reporting batch item failures

This is implemented in the Java events SDK as: aws-lambda-java-events/src/main/java/com/amazonaws/services/lambda/runtime/events/StreamsEventResponse.java

I don't know that adding a test here has any value, but happy to add one if you'd like.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[codecov-commenter]

Codecov Report

Merging #410 (ad4620d) into main (96ab249) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #410   +/-   ##
=======================================
  Coverage   71.66%   71.66%           
=======================================
  Files          19       19           
  Lines        1041     1041           
=======================================
  Hits          746      746           
  Misses        228      228           
  Partials       67       67           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 96ab249...ad4620d. Read the comment docs.

[bmoffatt]

Thanks! This looks applicable for SQS Partial Batch Failures too!
https://aws.amazon.com/about-aws/whats-new/2021/11/aws-lambda-partial-batch-response-sqs-event-source/
https://docs.aws.amazon.com/lambda/latest/dg/with-sqs.html#services-sqs-batchfailurereporting

Though it can be used across all 3 event sources, I'm thinking to proactively namespace the structs. eg: define KinesisEventResponse, DynamoDBEventResponse, SQSEventResponse

@carlzogh WDYT?

[carlzogh]

Though it can be used across all 3 event sources, I'm thinking to proactively namespace the structs. eg: define KinesisEventResponse, DynamoDBEventResponse, SQSEventResponse

Absolutely, thanks @bmoffatt - we've found it tricky in the Java events library to rename/cater for different event source types that seem similar at first, so accounting for those explicitly from the get-go is a good idea!

[shawnkoon]

Doing a pulse check, would love to see SQSEventResponse implemented.

Though it can be used across all 3 event sources, I'm thinking to proactively namespace the structs. eg: define KinesisEventResponse, DynamoDBEventResponse, SQSEventResponse

Is there a strategy on BatchItemFailure ex) if it should be name spaced to {SQS|Kinesis|DynamoDB|Stream}BatchItemFailure or just keep one BatchItemFailure somewhere? Happy to contribute

[lyoung-confluent]

I split up the structs (and child item failure structs) into different structs per each service (as well as adding SQS) and updated the description/title accordingly. I kept everything in streams.go instead of individual files though.

[bmoffatt]

LGTM, thanks!