Done.

Changed reporting to the Catalog with a batch of written files.
Changed synchronous reporting to the backend job by job to the
asynchronous reporting for batch of jobs.
Changed synchronous reporting to the EOS mgm to the asynchronous
reporting.

This new version locks the queues for less time.
Fixed a bug where the wrong lock (shared and not exclusive) was taken when removing empty queues
from the root entry.
Improved multiple iterations retrying (we can now retry on a new queue if one gets contructed
in the meantime.

This makes the system tests faster on HDD backed systems as mhvtl is an heavy user of fsync.

Fsync cost can go up to 100ms on HDD (+vm + hyperV).

This is a temporary solution before parallel request updating is deployed in RetrieveMount::getNextJobBatch().

Cleanup/reorder/rename for some fields.

Some cases of operations taking over a minute were seen practice.

The queue size division by the number of existing mount is only valid for archive mounts
where the queue is shared by each mount. In the case of retrieves, the criteria should be considered
vid by vid and the number of exiting mounts should not matter.

This commit fixes the following error encountered by the
Continuous Integration system and discovered and
reported by Eric:

Config Falling back to using libXrdCtaOfs.so
Plugin /lib64/libXrdCtaOfs.so: undefined symbol: _ZN3cta13xroot_plugins16XrdCtaFilesystem5FSctlEiR11XrdSfsFSctlR13XrdOucErrInfoPK12XrdSecEntity fslib libXrdCtaOfs.so
Config Unable to load fslib plugin libXrdCtaOfs.so
170804 02:37:03 558 XrootdConfig: Unable to create file system object via libXrdCtaOfs.so
170804 02:37:03 558 XrootdConfig: Unable to load file system.
------ xrootd protocol initialization failed.

The origin of the problem is the following commit that
completed removed the implemention of the
XrdCtaFilesystem::FSctl() method:

commit ea8d5241
Author: Michael Davis <michael.davis@cern.ch>
Date:   Thu Aug 3 10:54:49 2017 +0200

    [XrdSsi] Updates eos_messages.proto and deletes Opaque Query

    Update the protobuf file to the version required by EOS-CTA SSI
    interface and delete all source code that depends on the previous
    version (i.e. all the opaque query code).

This removal should have been a replacement as opposed
to a hard delete.  The XrdCtaFilesystem::FSctl() method
should have been re-implemented as follows:

int XrdCtaFilesystem::FSctl(const int cmd, XrdSfsFSctl &args, XrdOucErrInfo &eI
  (void)cmd; (void)args; (void)eInfo; (void)client;
  eInfo.setErrInfo(ENOTSUP, "Not supported.");
  return SFS_ERROR;
}

Problem can occur in case of lock expiration. The request is still updated and should be handled as such.
The previous behaviour led to orphaned objects.

The problem is only seen while fetching the queues for scheduling. This commit detect the situation, logs and
skips the queue.
Also fixed typo in exception name.

Update the protobuf file to the version required by EOS-CTA SSI
interface and delete all source code that depends on the previous
version (i.e. all the opaque query code).

The destructor attempted to release a non-locked lock when creation function MemQueue<Request, Queue>::sharedAddToNewQueue()
failed while populating the object. The reason for the failure itself is fixed in 9f90713f.

It was used in logging.

Added resetting of ArchiveQueue address in Helpers::getLockedAndFetchedQueue<ArchiveQueue>() retries.

Log added to ArchiveJob::~ArchiveJob() and ArchiveRequest::garbageCollect().
Removed deprecated functions from previous archive directory model (pre-catalogue).

The appearance and disappearance of the agents is totally asynchronous for the garbage collector.
For this reason, GC should tolerate deletion of object at any time. This commit fixes the case where the
object disappears shortly after the garbage collector decides to watch it.

ls' command. Fix spaces in outputs.

Purging Oracle DB recycle bin in init, otherwise CI DB size explodes because of the recycle bin content.

The locks in Rados have timeouts. They are needed in case a locker process dies without
releasing its lock. As we have some contention in heavily loaded situations, it can happen
that a process is till accessing objects while the lock is expired. To lessen the likeliness
of this situation, the timeout has been increased from 10s to 60s.

The backoff was ajusted using the MultithreadLockingInterface unit test, with printouts
allowing to visually see the effect of the backoff strategy. The printouts are committed,
but they are commented out.

The same unit test was fized as it used to create an empty object, which is not supported
anymore in order to be able to detect locking of non-existing objects (lock creates the object,
but we detect non-existence as it is empty and re-delete it.

This mechanism of empty object locking detection is also added to the async update of object
as it was missing there (and the backoff has been added there too).

Added unlocking a non-scoped lock if needed.
Added more information in logs.

Name of object was already present in some errors but not all.

DriveState.

- when failing to schedule.
- now list which drive has an existing mount (at schedule time as well.