We currently only cover the Recalls, and we still need to start the threads.

intended for protyping.
Retyped DiskWriteThreadPool's members to fixed length types.

MemBlock, MemManager, MemManagerClient, MigrationJob,
TapeReadFileTask, TapeReadTask, TapeSingleThreadInterface,
TapeReadSingleThread, TapeWriteTask, TaskInjector
into castor::tape::tapeserver::daemon

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

With this commit tapeserverd connects to the vdqm using Cgethostbyname().
It is planned to replace this use of Cgethostbyname() by getAddrInfo().

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

Eric found that the underlying C function getaddrinfo() is thread
safe because of RFC 3493.

The getaddrinfo() function will be used instead of the inetPton() function,
I am therefore removing inetPton() in order to reduce deadwood.

This new overloaded version still needs to be implemented.  It currently
throws an exception.

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

This version of connectToVdqm() is based on Cgethostbyname().  This is
a temporary implementation.  I would like that it is replaced by code
based around getaddrinfo() which is both standard and thread-safe on
linux and is therefore better than gethostbyname() whose rentrant
cousin gethostbyname_r() is a GNU extension.  According to the BSD
manual pages, the getaddrinfo() function is a replacement for and
provides more flexibility than gethostbyname().

I cannot find any information about the thread safety of getaddrinfo()
on MAC.

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