This prevented the passing of exceptions as output.
Also integrated the promise in the reporter class.

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.

Fixed lack of override specifier

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.

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 framework does not throw exceptions to the client, instead it puts
the exception in an Alert and calls the AlertCallback to log it.

* EOS->CTA is a Notification message
* CTA->EOS is a Response message (sent as Metadata)
* Optional Alert for extra log messages (sent as Alert)

A top-level string which is unassigned will be assigned a default value of empty
string. If we put it inside a nested message, then an unassigned string has no
value.

No wrapper for sent messages (as only one message type can be sent). Defines a
wrapper for received messages. Defines message types for errors and alerts.

Changes to protobuf breaks cta-xrootd_plugins-write-notification-msg, so
I removed it from the build in this branch.

The report of a file being archived will now timeout after
15 seconds when trying to connect to EOS.   The previous
timeout was 8 minutes.

The 8 minute timeout was so long that the "kill a stalled
data transfer session" logic would kick in before the
timeout expired.  This killing logic would then mask
the underlying problem.