Support extending job visibility timeout

[ali-essam]

When fetching a message from SQS, visibilityTimeout (Duration (in seconds) that the received messages are hidden from subsequent retrieve requests.) is determined at request time

In some cases, the timeout might not be clear during the request and the processing job might need more time to process the message. Currently, if the visibilityTimeout is less than the job processing time, that will cause the message to be back in the queue and visible to other workers to fetch again, causing double processing of the same message.

It's possible through SQS API to extend the timeout after fetching the message through ChangeMessageVisibility.

TODO: Implement this functionality in WTSQS.

[asadswvl]

@ali-essam Would you please elaborate this issue?

[ali-essam]

Hi @asadswvl, I have updated the issue description. If you're interested in this feature, let me know and we can work together on its implementation.