Wrong reported size or checksum now simply causes the errro to be reported and the file to be
skipped during a tape mount, instead of unmounting the tape, making queue consumption faster
in such cases.

The DiskReadTask task issues DiskFile::size to validate the file size.
As Xroot protocol always return the StatInfo on open and as tape files
are immutable (even if not files are not locked, this calling stat and
then read doesn't guarantee that file is not changed), there are no
needs to enforce the xroot client to ignore stat cache.

- fix the config/log file locations
- remove some obsolete config options
- describe TpConfigPath and BufferCount

Add the UseEncryption drive config with a default value of yes.

A tape mount is stoped if the external encryption script is empty and UseEncryption is yes

Allow retrieve to continue if disk system configuration is removed by processing jobs as if they had no disk system (#1076)

Refactor the RecallTaskInjector to limit the number of tasks passed
at once to the TapeReadSingleThread for a tape with RAO and to reserve
disk space in smaller batchs

In every call of RecallTaskInjector::synchronousFetch the injector
will try to pop jobs from the queue so that it holds an ammount of
work equal to the limit of files or bytes imposed by the RAO
implementation or by the value given by the
BulkRequestRecallMaxBytes and BulkRequestRecallMaxFiles config
options in /etc/cta/cta-taped.conf.

In every call of RecallTaskInjector::injectBulkRecalls the
RecallTaskInjector will inject a set of tasks limited by the
BulkRequestRecallMaxBytes and BulkRequestRecallMaxFiles config
options in /etc/cta/cta-taped.conf to the TapeReadSingleThread
and DiskWriteThreadPool.

The disk space reservation is done once for every job batch (instead of
all the disk space being reserved when the jobs are popped)

This prevents tapeservers with RAO from reserving a large amount
of the disk buffer upfront, which would cause the buffer to fill quickly
by a few drives, which cannot fill it fast enough