Use consistent name of Automation parameters save/saveDocument

Various Automation operations use a save or saveDocument parameter. Both are sometimes used to flag that the document must be saved, but in some cases the save parameter is used to flag saving the session instead of the document.

This should be made consistent:

• saveDocument to save the document
• saveSession to save the session

And keep but deprecate the save parameter when it's currently used.

At least the following operations classes use save for the session:

• AddItemToListProperty
• CopySchema
• RemoveItemFromListProperty
• RemoveProxies
• ResetSchema

At least the following operations classes use save for the document:

• AddEntryToMultiValuedProperty
• AttachBlob
• ExtractTextFromPDFOp
• PDFExtractInfoOperation
• PDFExtractTextOperation
• PDFInfoToFieldsOp
• PutSimpleConfParam
• PutSimpleConfParams
• RemoveDocumentBlob
• RemoveEntryOfMultiValuedProperty
• RemoveProperty
• SetBlobFileName
• SetDocumentBlob
• SetDocumentProperty
• UpdateDocument
• WriteMetadataToBinaryFromDocument