Removed deprecated structures from archiveNS and nameserver namespaces. Removed RetrieveToFileRequest.

Deleted tests for scheduler features that moved to the catalogue.
Factored out the common unit test initialization.

The values are now hardcoded.
Cleanup:
  - Removed object store unit tests for data now in the catalogue.
  - Removed now unnecessary 2nd step addition of retry limits to archive jobs.
  - Removed deprecated ArchiveToFileRequest files.

Changed a few comments and redirected the result of the command line to std::out instead of std::err

Added binned running counters (ValueCoundMap) for managing summaries of priorities in object store queues.
Simplified the interfaces to the getPendingArchiveJobs and getPendingRetrieveJobs functions in Scheduler and SchedulerDB.
Removed now unused ArchiveToTapeCopyRequest.
Removed long unused mockScheduler.
Removed _old_protoype files.

Propagating the return code of a frontend operation back to the client, also properly handling server timeout

Fixed small bug in nsfileid comparison in tape write task, and added ctacatalogue in xroot plugin linkage

PLEASE NOTE:

    The tapeserverd daemon (ProcessForker::runDataTransferSession)
    now reads the connection details of the catalogue database from
    the following configuration file at the beginning on each tape
    mount:

        /etc/cta/cta_catalogue_db.conf

    Installing the CTA rpms will install the following example file:

        /etc/cta/cta_catalogue_db.conf.example

    This example file document the syntax of the database connect
    details.

    For the time being the contents of cta_catalogue_db.conf should
    simple be:

        in_memory

    This means the tapeserverd daemon will use an in-memory
    catalogue database.

PLEASE NOTE:

The XROOT plugin (CTA front end) now reads the connect details of
the catalogue database from the following configuration file:

    /etc/cta/cta_catalogue_db.conf

Installing the CTA rpms will install the following example file:

    /etc/cta/cta_catalogue_db.conf.example

This example file document the syntax of the database connect
details.

For the time being the contents of cta_catalogue_db.conf should
simple be:

    in_memory

This means the CTA front end will use an in-memory catalogue
database.