fix(idempotency): serialize UUID and datetime fields in dataclass payloads

[Om-singhaI]

Issue number: closes #8500

Summary

Changes

Adds an encoder used only when generating idempotency key and payload validation hashes. It supports UUID, date, datetime, time, plain Enum, and path values while giving the existing encoder priority. This preserves existing representations, including enums based on Decimal.

Dataclass inputs still go through dataclasses.asdict(). The additional conversions happen after event_key_jmespath and payload_validation_jmespath are evaluated, so built-in and custom functions receive the original field types. Dictionary inputs use the same hash encoder. Response serialization is unchanged.

User experience

A dataclass containing UUID or datetime fields currently fails while hashing the input, before the function runs. These inputs can now be processed and subsequent calls reuse the saved result.

Compatibility tests assert the exact DynamoDB keys and validation hashes for previously supported inputs, then return an existing record without executing the function. Additional tests cover replay with local caching enabled and disabled, changed-payload rejection, and unsupported types.

Validation

• Python 3.14: 191 idempotency tests passed, including DynamoDB, Pydantic, and Redis cases.
• Python 3.10 without Pydantic installed: 149 tests passed.
• Five compatibility regression cases fail on the original PR and pass with the follow-up.
• Idempotency coverage: 98.30%; the new encoder has 100% line and branch coverage.
• Ruff, mypy, Bandit, complexity checks, and Markdown lint passed.

---

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

[sonarqubecloud]

Quality Gate passed

Issues
2 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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.80%. Comparing base (562cd2c) to head (8686fc6).
⚠️ Report is 2 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #8501   +/-   ##
========================================
  Coverage    96.80%   96.80%           
========================================
  Files          310      310           
  Lines        15579    15594   +15     
  Branches      1358     1361    +3     
========================================
+ Hits         15081    15096   +15     
  Misses         362      362           
  Partials       136      136           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[leandrodamascena]

Thanks for catching this, @Om-singhaI! I pushed a follow-up that moves the conversion to the hashing step, after JMESPath evaluation. This preserves existing encodings, including Decimal-based enums, and lets expressions and custom functions keep working with the original types.

I also added regression tests to verify that existing records are reused without executing the function again.

[mergify]

This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again.