[BUG] ApproximateCreationDateTime from DynamoDBStreamRecord in milliseconds when originating from Kinesis, not seconds.

This is essentially the same issue as https://github.com/aws/aws-lambda-dotnet/issues/839, but without crashing deserialization, which I'm guessing is due to the use of float64 that avoids overflowing with the larger value to deserialize. The relevant points of discussion are:

• https://github.com/aws/aws-lambda-dotnet/issues/839#issuecomment-1055736269
• https://github.com/aws/aws-lambda-dotnet/issues/839#issuecomment-1063559586

It seems that the value of ApproximateCreationDateTime will be in seconds when coming from a DynamoDB Stream, but in milliseconds when coming from a Kinesis Stream:

• DynamoDB Streams - https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_streams_StreamRecord.html

The approximate date and time when the stream record was created, in UNIX epoch time format and rounded down to the closest second

• Kinesis - https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/kds.html

ApproximateCreationDateTime indicates the time of the modification in milliseconds.

There appears to be an internal ticket that's being tracked, so I wanted to open an issue here as well for AWS to monitor and hopefully resolve in the near future. Thanks!

Inizia dal campo ApproximateCreationDateTime di DynamoDBStreamRecord e confrontane la gestione per i record Kinesis e DynamoDB Stream. Leggi prima l’issue aws-lambda-dotnet collegata e la documentazione AWS sugli stream; il lavoro è completo quando il valore usa l’unità corretta per ciascuna origine e il comportamento di deserializzazione è coperto da un controllo di regressione appropriato.