New owncloud propagator that skip the vio abstraction layer

The vio abstraction layer within csync is inneficient for the owncloud
use case because not all calls maps well to the POSIX interface. We can
be much more efficient by doing exactly what we need.

Also, this will allow us to scedule better the calls and possibly to use
threads.
Add owncloudcmd

A simple commandline client like ocsync.
The goal is to be used bu the t1.pl test
Handle renames
Implement renaming on windows

(Not actually tested)
move command line client into bin dir
Proper error reporting of propagator - WIP
More error handling of propagator, some cleanups.
Enable the backup of conflicts files in owncloudcmd
propagator-ng:  handle conflict

Always download the file from the server.
And if they are equals, ignore the conflict
Fix compilation after previous rebase
propagator-ng: get the etag also in the GET request
style:  use _ in front of member variable
Improve error handling, add error string to each individual file item.
Really return true in case of error.
Created a test file for ownCloudPropagator. Not much in yet.
propagator-ng: Emit the fileReceived signal
propagator-ng:  set the modtime on downloaded files
propagator-ng:  be able to resume download
propagator-ng:  resume uploads

Currently i think it corrupt the files
remove some FIXME