Don't log errors when retention not in compliance mode and bucket has no object lock

When retention is not in compliance mode (i.e., is in governance mode), there is no need for an underlying bucket to have object lock activated, which means that the regular bucket (not configured for records mode) can be used.

However in this situation currently the backend still attempts to set retention (or a legal hold) on the underlying blob, which fails because it only works when object lock is activated on the bucket, and an error is logged.

—> change the code to detect this situation and not attempt to set retention or legal hold on the underlying blob