fix(idempotency): record validation not using hash

[dreamorosi]

Description of your changes

As reported in the linked issue, the persistence layer for the Idempotency utility was not using the payload hash when payload validation was enabled. This was caused by two issues:

• While the hash for the payload was saved in DynamoDB under the attribute validation, on subsequent requests the value was discarded at runtime and not used when instantiating the IdempotencyRecord
• The hash being generated and stored was using the full payload even when a JMESPath expression was specified, instead of using the expression to identify a subset of the payload. This would have caused the validation to always fail since the JMESPath expression was used in the control item but not in the stored one.

Both issues have been fixed in this PR. The PR also contains an unrelated change that aligns the name of the in progress expiry attribute with the reference implementation (in_progress_expiration).

Related issues, RFCs

Issue number: #1499

Checklist

• My changes meet the tenets criteria
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my change is effective and works
• The PR title follows the conventional commit semantics

Breaking change checklist

Is it a breaking change?: NO

• I have documented the migration process
• I have added, implemented necessary warnings (if it can live side by side)

---

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.

[brianhyder]

I pulled the branch and tested it. This fixes the issue I was seeing earlier. Thank you, all!