Changed 'catch (cta::exception::Exception ex)' to 'catch (cta::exception::Exception &ex)' in order to avoid error: catching polymorphic type ‘class cta::exception::Exception’ by value

Status of repack retrieve request changed to RJS_Succeeded, started to insert the repack retrieve request into RetrieveQueueToReportToRepackForSuccess

Repack RetrieveRequest reported as success after mount and retrieve successful (expandRepackRequest)

of VO and Density"

Added MEDIA_TYPE and VENDOR columns to TAPE table and upgraded xrootd-ssi-protobuf-interface to v0.29

DataTransferSessionTapeFullMigration and DataTransferSessionTapeFullOnFlushMigration now count the first files archived to tape as opposed to relying on the values of the archive file IDs

Because ToReport queues need to construct RetrieveJob objects which are
not associated with a mount

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.

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.

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.

We now leave a placeholder on the tape and carry on in this case. The errors will eventually clear the
archive request.

The disk read task hangs in this case. The tape write taks is still created, will leave a placeholder on the
tape (to be implemented) and count an error for the request.

cta/CTA#296 Temporary disabled unit-test OStoreDBPlusMockSchedulerTestVFS/DataTransferSessionTest.DataTransferSessionMissingFilesMigration/0

Modified CMakeLists.txt files to apply -Wno-unused-function for GCC 6 and above.  It was GCC 7 and above before.

This setup allows reproducing a but seen in system tests.

This is validated in a unit test.

The catalogue can receive polymorphic items as input for recording.
The strict sequencing of fSeqs is still enforced.
Currently, 2 items types are recorded: files and placehoders.
Files are recorded to the tape catalogue, while place holders are not,
but they are used to enforce the fSeq sequencing.

When no data is received for a given file, the tape server will
leave a placeholder on tape an carry on with the writing of the
following files, avoiding a tape unmount.

Updated unit test.

The error(s) gets recorded at failure time, and the list is printed at
job deletion time.

This version is not data safe as the request is created late, right after
referencing the job to the queue.

The top half goes as far as when the request is safe in the object store.
At that point, the bottom half is launched in a new thread, and success is returned
the called. This will enable lower latency for the users while retaining
the same data safety.

This version is experimental aas it spans an undetermined number of threads. A more controlled
version with a work queue should be implenented on the long run.