fix(parser): change ApproximateCreationDateTime field to datetime in DynamoDBStreamChangedRecordModel

[waveFrontSet]

Issue number: #3048

Summary

This promotes ApproximateCreationDateTime to a datetime object (instead of date) so that pydantic v2 will correctly deserialize it when parsing DynamoDB stream events.

Changes

Only the type of ApproximateCreationDateTime has changed.

User experience

If users would like to rely on a proper date object after the change, they need to use datetime's date method. Here's how that may look like.

Before the change

from aws_lambda_powertools.utilities.parser.models import DynamoDBStreamChangedRecordModel

changed_record = {
    "ApproximateCreationDateTime": 1479499740,
    "Keys": {
        "Timestamp": {"S": "2016-11-18:12:09:36"},
        "Username": {"S": "John Doe"},
    },
    "NewImage": {
        "Timestamp": {"S": "2016-11-18:12:09:36"},
        "Message": {"S": "This is a bark from the Woofer social network"},
        "Username": {"S": "John Doe"},
    },
    "SequenceNumber": "13021600000000001596893679",
    "SizeBytes": 112,
    "StreamViewType": "NEW_IMAGE",
}
model = DynamoDBStreamChangedRecordModel.model_validate(changed_record)
creation_date = model.ApproximateCreationDateTime
# Carry on with evaluating the date...

After the change

# Parse the model just like before...
creation_date = model.ApproximateCreationDateTime.date()
# Carry on with evaluating the date...

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• Meet tenets criteria
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

Is this a breaking change?

Yes, this could break existing code using Pydantic V1 that examines `ApproximateCreationDateTime` and relies on it being a proper date object.

RFC issue number:

Checklist:

• Migration process documented
• Implement warnings (if it can live side by side)

Acknowledgment

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

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[leandrodamascena]

Approved! 😄

[boring-cyborg]

Awesome work, congrats on your first merged pull request and thank you for helping improve everyone's experience!