Renamed CTA/tapeserver/castor to CTA/tapeserver/castor_checkout in preparation for the moving the sub-directory CTA/tapeserver/castor/castor up the directory tree

Added a new m_moverHandlerPort member to the diskFileFactory class, so the new xroot-c2fs URLs can be implemented.
Propagated the value from castor.conf through the constructors of the DiskThreadPools and the DataTranferSessions.

Propagated references to the watchdog to disk and tape threads and tasks.
Added a maps for storing the count of all errors that occured during the session.
Added propagation of the counts to the initial process.
Added error reporting in disk and tapes threads and tasks by using a string marker
allowing to know which part went wrong in high level exception. Exceptions then
bumps up the count in the watchdog (synchronously), and the watchdog sends the
new count to the initial thread later (in the watchdog's thread).
Plus some missing logs fixed when an exception is thrown in a disk write task.

Added interface to reference the recall watchdog to the recall disk thread pool.
Next: Do same for migration. Actually store the reference. Add new error map storing in watchdog. Add error reporting in tape and disk threads.

WIP: Added missing file ID for disk write thread. Added missing error log when an exception is thrown in a disk write task.

WIP: switching to CASTOR-4839 tapeserverd: task injector should decide on closing the session earlier

WIP. Next: log unmount errors (in the RAII)

Finished error counting in data threads.

CASTOR-4739: tapeserverd should support localfile, rfio, xroot and rados striper access for disk files

Moved the call to getConfEntString(XROOT, PrivateKey, /opt/xrootd/keys/key.pem one step up to allow
unit testing in environments without a castor.conf

Tapeserverd now support file://, root:// rfio:// and radosStriper:// URLs, on top of heuristic protocol guessing from the hostname:[/]path synthax.
The rados striper version is not yet fleshed out yet.
The xroot client used for this is the latest object oriented client (XrdCl::File).

Split the memory managers into headers and implementation.
Cut the number of includes by forward declaring classes.

Added Doxygen comments in DiskWriteTask.hpp.
Reformatted the code in DiskWriteTask.cpp, DiskWriteTask.cpp and added logging.
Removed unnecessary members m_maxFilesReq and m_maxBytesReq from DiskWriteThreadPool and adapted callers.

Thus, The real reporters do not inherit publicly from it => Changed all the lines of coded that had to be changed

Compute it on DiskWriteTask and report it to the Client. Tests and interfaces have changed consequently

RecallMemoryManager is the memory manager dedicated to the recall. All recall-related files are now using RecallMemoryManager

Some ambigous namespaces no well supported by g++ 4.1