Issue #275 - Fix visibility timeout error handler

[rafael-pb]

Description

• Added await to changeMessageVisibility and changeMessageVisibilityBatchBatch calls to SQS
• Convert error using toSQSError when catching visibility timeout errors
• Added unit tests

Motivation and Context

Fixes issue #275: visibility timeout changes are mostly used by the heartbeat (inside a Timer) that does not catch errors nor wait for the promise to be resolved. In those cases, it caused an unhandled exception/rejection.

Types of changes

• 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)

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.

[RobPethick]

We are also experiencing this error

[RobPethick]

@memsb thank you for merging this one - it is so important to us. Could you release an updated npm version for this?

[memsb]

Version 5.7 was released today and includes this PR

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.