feat(idempotency): Allow durable function to replay

[ConnorKirk]

Summary

This PR adds support for Durable Functions to the Idempotency Utility.
In testing, we discovered that the Idempotency utility did not work with Durable Functions when they suspended and replayed. This is because the replay appeared like a duplicate, so raised an IdempotencyAlreadyInProgressError

We use the DurableMode property on the DurableContext object to track if this is a new execution, or a replay of an prior execution.

The behaviour of the handler is the same, except when it's a previously seen payload "in progress" and the DurableMode is REPLAY_MODE. Then the execution will continue, where previously it would have raised the error IdempotencyAlreadyInProgressError

Changes

• Check the context type in makeIdempotent. If it's a durable context, extract the lambda context and the DurableMode.
• Add a new optional parameter to the IdempotentHandler.handler() method, durableMode.
• Update IdempotentHandler to check if the execution is in REPLAY_MODE when IdempotencyAlreadyInProgressError is thrown.
• Add tests to IdempotentHandler.test.js
• Add test to makeIdempotent.test.js

Notes

• It's missing e2e tests. These will be added in a future PR.
• We use context.getTimeInMillis() to calculate the expiry time of the INPROGRESS status. Duplicate payloads received after that expiry time will be allowed. In a durable execution, the length of the workflow can be up to 1 year, across multiple lambda invocations. This is longer than the maximum 15 minutes that an INPROGRESS status can currently have. Idempotency records for long running workflows will not be protected from duplicate invokes beyond the first 15 minutes of their life.

Please add the issue number below, if no issue is present the PR might get blocked and not be reviewed

Issue number: closes #4831

---

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

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dreamorosi]

Thank you

[ConnorKirk]

I've opened #4839 to track the E2E test task