Add ability to stop winmsa from changing owner
Two reasons for this:
(A) there are times when user may want to preserve file ownership, but have file re-ACLed.
It was observed on a call where winmsa's chown operation, which operated according to design, resulted in unintended permissions change across directory that was moved.
0) User may have had a windows configuration that transferred security attributes from source to destination.
1) User created a dir (thus becoming owner). New directory inherited permissions from parent directory.
2) User then moved another directory into the newly created one.
Winmsa properly pushed the parent directory's ACL, but then windows client re-applied the source directory's ACL immediately after move completed (seen in pcap and log.smbd). These ACL operations succeeded despite the user not having explicit permissions to change the ACL because he was the owner of all the files in question. Turning off chown may help limit the impact of misconfigured clients.