SetAndDeleteContentTest does not propertly handle documents whose content stream is required

According to CMIS specification, the Repository MUST throw a constraint exception if the Object's Object-Type definition "contentStreamAllowed" attribute is set to "required".

Running SetAndDeleteContentTest on a document whose content stream is required fails due to a CmisConstraintException thrown by deleteContentStream.

To properly handle this scenario, one can either:

• catch CmisConstraintException thrown by deleteContentStream
• check the value of contentStreamAllowed for the target object prior to calling deleteContentStream, and delete content only if it is not required