Attach failed message ids to error object

[knicola]

Description:
Throw a custom error, when messages fail to send, with an additional property to expose the failed message ids for programmatic access.

Type of change:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Why is this change required?:
In cases where we have to take additional steps for the failed messages, we have to parse the error message in order to get their IDs.

Code changes:

• Add a custom FailedMessagesError error class, with a failedMessages property of type string[] to hold the IDs of the messages that failed to send.

---

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[nicholasgriffintn]

Hey, sorry, super busy this week, I'm gonna slot some time to look into this on Friday hopefully, if not before.

[knicola]

I have read the CLA Document and I hereby sign the CLA

[knicola]

¯\_(ツ)_/¯

[vizeke]

I suggest saving the entire BatchResultErrorEntry from the sqs.send response in the FailedMessagesError. This way will be easier to track what's going wrong.

[nicholasgriffintn]

Sorry I just realised that I am super late here, sorry, holiday and crazy work period.

This looks fine to me, although I do need to investigate if this is potentially breaking, probably not.

[nicholasgriffintn]

Merging the live, will mark this as a major change just to be safe.