Increased queue depth in helgrind reports.
Added locking in a constructor to make helgrind happy.
Added suppression for helgrind finding races in synchronization functions (?)

This was a slight variation of the previous case (again a complain on mutex_destroy).

https://st-ci.cern.ch/job/CTA-autotest/1034/consoleFull

The first 6 issues are about places where error conditions of the pthread mutexes are validated (And a suppression is required).
The 7th one is about a race between the unlocking of the mutex itself and it deletion. We seupresed this error also.

Replaced castor file header with CTA file header

Moved castor::server::
  BlockingQueue
  Semaphores
  AtomicCounter
  AtomicFlag
into cta::threading::

Removed unused files.
Added missed unittests.

Fixed spurious file closing on failure to open in BackendVFS.

Ported DataTransferSessionTest unit test  DataTransferSessionGooddayMigration and DataTransferSessionEmptyOnVolReq.

Renamed cta-oraUnitTests to cta-catalogueUnitTests because there is more than one supported database type

This allows spawning a subprocess from a process using lots of memory without issue.
Otherwise the kernel will make sure we have in memeory+swap enough to accomodate 2*size of the parent process.

Re-enabled the helgrind tests that triggered it.

relies on global variables managing files which were deleted on child process exit.
Helgrind is currently disabled for the multiprocess unit test as it makes it fail.

Added silencing of valgrind information for child processes.
Added protocol buffers cleanup at the end of unit tests.

Added new make targets for helgrind and valgrind.

Created a new class ConfigurationFile that turns a text file into a double map of categories/keys entries.
The map also contains the line number from which the configuration is comming.