NSFS | list-object - is_latest is always set to first delete-marker after pagination

[nadavMiz]

Environment info

• NooBaa Version: VERSION
• Platform: Kubernetes 1.14.1 | minikube 1.1.1 | OpenShift 4.1 | other: specify

currently we caluclate if a delete marker is latest by checking if there is a previous delete marker in the list
if we call list-object with key marker we start from the middle of the list. in that case if the first element on the list is a delete marker the previous delete marker will not appear on the list. causing us to incorrectly set it to be a delete marker

Actual behavior

1. first delete marker after pagination is always set to be latest

Expected behavior

1.delete marker is set to be latest only if it actually is latest

Steps to reproduce

1. list_object with key_marker and version_marker of a non latest
   s3api-nadav list-object-versions --bucket nadav-bucket --key-marker <key> --version-id-marker <version-id>
2. first element is the delete marker

More information - Screenshots / Logs / Other output

[github-actions]

This issue had no activity for too long - it will now be labeled stale. Update it to prevent it from getting closed.