Fix detection of active/orphaned binaries in S3 storage

When marking the orphaned binaries with a S3 configuration using a bucket prefix, the system detects no active binaries and marks all the binaries as orphans whereas it should not.

This is a critical issue because all the blobs could be removed from the binary store if the user checks the "Delete orphaned binaries" box before activating.