Conflicts:
	castor/tape/tapeserver/daemon/RecallTaskInjector.hpp

Changed a few includes from RecallTaskInjector to forward decleration and had to add them back in orther files

Added a bunch of comments to TapeWriteTask, TapeWriteSingleThread, TapeSingleThreadInterface, TapeReadSingleThread

Because it was never set up mcorrectly and hard coded to zero

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.

Added a bunch of comments for MigrationTaskInjector,MigrationReportPacker, RecallTaskInjector and DataFifo

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

Fixed unnecessary virtual declarations in classes without inheritance (only detected by the SLC5 compiler).

Removed interface classes DiskReadTaskInterface, DiskWriteTaskInterface, DiskThreadPoolInterface

Moved MemException from castor::tape::tapeserver::daemon to castor::tape::exceptions and changed the uses in the code
The tapeserver/daemon/Exception.hpp was empty after that, he has been removed

The marshal code of AdminAcceptHandler was copied from some relatively
older code that did not do all of the usual marshalling checks.  This
commit effectively updates the code of the marshalTapeStatReplyMsg()
method.