Relaxed constrain on frequency for flusing report and added logging&report to client in case of mismatch between the report's type for the end of session and the presence of an error
Now we call reportEndOfSessionWithErrors if there is an actual error or a mismatch (that implies a bug in the code). Flushing is done as soon as the number of reports is >= frequency (instead of >)

Add logging and report to client in case of mismatch between the report's type for the end of session and the presence of an error
Now we call reportEndOfSessionWithErrors if there is an actual error or a mismatch (that implies a bug in the code)

Recalled files are now logged and the list of reports is cleaned-up after reporting the statuses to the client

MigrationReportPackerTest.cpp and RecallTaskInjectorTest.cpp had both their FakeClient class (which was a waste of time). They now use the merged class which is FakeClient.hpp

log, client interface and m_listReports are now inherited from the base class

Also changed FakeClient classes into the tests files  to add an empty implementation of reportRecallResults

The logContext was received as a reference and shared, thus causing race conditions and bugs because the class is not thread safe

FakeClient::getFilesToRecall - remove print-testament to put instead an assert to make sure the index is within the bounds

ClientInterface gained reportMigrationResults,reportEndOfSession(WithError) and VolumeInfod moved also to ClientInterface

RecallJob has been substituted by FileToRecallStruct and MockTapeGateaway by ClientInterface

The test and mount session have been adapted to the previous developments.
Mount session now goes as far as opening the tape drive.

This options allows us to prepare the contents of a drive for a unit test.
This function is only implemented for the fake systems and the drives of type VIRTUAL, so it is only available
for test environments.

Replaced the ad-hoc container castor::tape::drives::Drive by a factory function castor::tape::drives::DriveFactory.

Adapted the use in all the tests (with auto_ptr).

We need to make sure the coverage of the UT is enough

It now uses interfaces' types (TapeSingleThreadInterface<>, ClientInterface, and DiskThreadPoolInterface<>)instead of the types of the derived classes for its arguments

Thus the RecallTaskInjectorTest.cpp does not complain about link error

Indeed, there was a clash into auto_ptr destructor (which does a delete) and the allocation which was done using new[]