Changed the lifecycle of the ArchiveRequest to handle the various
combinations of several jobs and their respective success/failures.
Most notably, the request now holds a reportdecided boolan, which
is set when decing to report. This happens when failing to archive
one copy (first failure), or when all copies are transferred (success
for all copies).

Added support for in-mount retries. On falure, the job will be
requeued (with a chance to pick it up again) in the same session
if sane session retries are not exceeded. Otherwise, the job is
left owned by the session, to be picked up by the garbage collector
at tape unmount.

Made disk reporter generic, dealing with both success and failure.
Improved mount policy support fir queueing.

Expanded information avaible in popped element from archive queues.

Added optional parameters to ArchiveRequest::asyncUpdateJobOwner() to
cover various cases.

Updated the archive job statuses.

Clarified naming of functions (transfer/report failure instead of bare
\"failure\").

Updated garbage collector for new archive job statuses.

Added support for report retries and batch reporting in the scheduler
database.

Updated obsolete wording in MigrationReportPacker log messages and error
counts.

Their poping of elements will be indifferent of number of bytes.

This class will handle reporting like the GarbageCollector class
does for garbage collection.

Adapted the interface of scheduler and ArchiveRequests to allow delegating
reporting to the disk report runner.

This commit is not functionnal. We still need to:
- Implement the ToReport/Failed queues interface.
- Adapt the queueing in the scheduler/ArchiveMount
- Implement the popping of jobs to report.
- Implement the async reporter for the files.
- Develop the user interface for failed requests.

..and other minor comment fixes.

The ArchiveRequest ownership at the request level has been deprecated in a preivous commit.
The jobs are now individually owned.

"ToTransfer" are to be picked up by tape sessions.
"ToReport" Includes both successes and failures to report, as the mechanism to report is the same.
   They will be handled by the reporter, which shares the single thread of the garbage collector.
"Failed" Will be a (possibly non-queue) container which will contain the failed requests. The operators
   will be able to examine, relaunch or abandon those requests.

The states and lifecycles of the requests have been reworked to reflect this lifecycle too.
The container algorithmes have been adapted to handle the multiple queue/container types.

Fixed lack of override specifier

Changed deafult release from 0 to 1 because 0 should never be used, see https://fedoraproject.org/wiki/Packaging:Versioning

Fixed.

Fixed

Enabling EOS TAG repo for nighly regression tests: if these fail we can now complain to the EOS team.

Upgraded to EOS 4.3.8-20180821144441gitbf49ffa in order to get the FST that does not fail an end-user close() when there is an error with the CTA frontend

Reverted commit of submodule xrootd-ssi-protobuf-interface to b92937743ef5f2eaf1e30336519c0e7ee055e6b2 in order to make the CI green again

- timeout limit increased to 600s
- drive status is no longer set to Unknown
- only effect of exceeding the timeout limit is to display the word
  STALE beside the update time

USerError will prevent the frontend from logging a stack trace.
File path will allow easier identification of problem files.

The tape write task not lister anymore to the memory manager for zero length files.

A retry might sneak into the session (depending of end of sessions and reporting speeds).
Relaxed the test criteria for this case.

Done.