S3 binary manager should not use Etag for transfer checks when encryption is enabled

By default S3 Binary Manager uses the S3-side computed MD5 digest provided in the Etag as a cheap integrity check for blob transfer.

This is no longer possible to compute when S3 encryption is enabled as it would require nuxeo to encrypt the blob on it's own side just for the sake of that check.