fix(data-classes): ensure lazy initialization for Cognito token generation response properties

[nc-dirknilius]

Issue number: closes #7651

Summary

Fixed lazy initialization behavior in Cognito User Pool Pre Token Generation trigger event response properties to ensure consistent state management and prevent None return values when accessing nested token configuration objects.

The PreTokenGenerationTriggerEventResponse and PreTokenGenerationV2TriggerEvent response classes had inconsistent lazy initialization behavior:

1. In ClaimsAndScopeOverrideDetails, the id_token_generation and access_token_generation properties could return None when the underlying data didn't exist yet, forcing users to handle None cases.

2. In PreTokenGenerationTriggerEventResponse.claims_override_details and PreTokenGenerationTriggerV2EventResponse.claims_scope_override_details, the properties used self.get() which created a new dictionary on every access instead of initializing the underlying _data dictionary once.

This meant that modifications to nested properties wouldn't persist correctly, as each property access would create a fresh wrapper around a new empty dictionary rather than modifying the event's actual data structure.

Changes

Updated the property implementations to use consistent lazy initialization pattern:

1. Changed id_token_generation and access_token_generation properties from returning TokenClaimsAndScopeOverrideDetails | None to always returning TokenClaimsAndScopeOverrideDetails by initializing an empty dict in _data if not present.

2. Modified claims_override_details and claims_scope_override_details properties to check and initialize their respective keys in self._data (instead of using self.get()), ensuring all modifications are made to the same underlying dictionary that will be included in the final event response.

This aligns with the existing pattern used in other trigger event response classes and ensures that users can chain property access and modifications without encountering None values or losing changes.

• test_cognito_pre_token_generation_trigger_event: Validates that claims_override_details properties can be accessed and modified, with changes persisting through the event object
• test_cognito_pre_token_v2_generation_trigger_event: Validates that claims_scope_override_details and its nested id_token_generation and access_token_generation properties can be accessed and modified with proper persistence of changes
• Both tests verify the lazy initialization behavior when properties are explicitly set to None in the raw event data

User experience

The user can now properly use the class:

event.response.claims_override_details.claims_to_add_or_override = { "test": "value" }

# or
event.response.claims_scope_override_details.id_token_generation.claims_to_add_or_override = { "test": "value" }

# or
event.response.claims_scope_override_details.access_token_generation.claims_to_add_or_override = { "test": "value" }

This was not working before as stated above. Even though there was some tests around that feature, the tests implemented poorly and covered the actual problem. The tests where updated to actually test the final event data.

---

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.

[boring-cyborg]

Thanks a lot for your first contribution! Please check out our contributing guidelines and don't hesitate to ask whatever you need.
In the meantime, check out the #python channel on our Powertools for AWS Lambda Discord: Invite link

[anafalcao]

Hi @nc-dirknilius ! Thanks for the PR, I see some checks are failing, can you address them? let me know if you need any help

[nc-dirknilius]

Hi @nc-dirknilius ! Thanks for the PR, I see some checks are failing, can you address them? let me know if you need any help

Hi @anafalcao, I fixed the linter finding. Pls re-check.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.52%. Comparing base (f77c259) to head (04a6147).

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #7653   +/-   ##
========================================
  Coverage    96.52%   96.52%           
========================================
  Files          275      275           
  Lines        13117    13123    +6     
  Branches       986      990    +4     
========================================
+ Hits         12661    12667    +6     
  Misses         353      353           
  Partials       103      103           

☔ View full report in Codecov by Sentry.
📢 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.

[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

[leandrodamascena]

Assigning to me to review this by Monday.