fix: SQS Consume should delete the message after use

[loicmathieu]

Fixes #155

[anna-geller]

I got the chance to QA this and the deletion is working now

however, the pattern from the issue seems worth revisiting in the future

use case: two flows, flow A and B

• flow A publishes a message to SQS
• flow B has SQS trigger + a task to consume a message from the same queue. it only starts after A finished. But this flow B will not consume the message from A as you would expect - somehow, this message sent from flow A is lost. instead, it only starts polling and to make it stop, you would need to send another message e.g. by triggering flow A again

so the end result is that you need 2 messages to make this pattern work - one message that would only trigger flow B and another message that would be the actual message that needs to be processed by flow B