[BUG] S3 Scan has potential to filter out objects with the same timestamp

[graytaylor0]

Describe the bug
Scheduled S3 Scan filters out objects by checking a global state item that contains the timestamp of the most recent object that was processed during the previous scan. (

data-prepper/data-prepper-plugins/s3-source/src/main/java/org/opensearch/dataprepper/plugins/source/s3/S3ScanPartitionCreationSupplier.java

Line 168 in 503b774

return s3Object.lastModified().compareTo(lastProcessedObjectTimestamp) > 0;

)

This has the potential to skip objects that are missed in the scan, but created with the same timestamp.

Expected behavior
Do not filter out objects that have a timestamp equal to the last modified timestamp

Additional context
Add any other context about the problem here.

[jw-amazon]

To work around the bug, do we have to keep the timestamp of the objects different when dropping the objects into s3 ingest folder?