This commit adds the feature of querying the drive for the
Recommended Access Order (RAO) of a series of files and adds
a test file for this feature.

Changes of this commit:
  *  Extend the DriveInterface with a virtual method queryRAO
which takes as parameter the name of the file containing a set
of files for which the RAO is requested. The line format of this
file is the following:

FILE_ID:BLOCK_START:BLOCK_END

  *  Extend DriveGeneric class with the implementation of the
method queryRAO, along with a few other auxiliary methods; some
key auxiliary methods are getLimitUDS, generateRAO, receiveRAO

  *  Add method queryRAO in object FakeDrive returning Exception:
Not Implemented

  *  Add auxiliary constants and structures in a new 'RAO' namespace

  *  Add test file: BasicReadWriteTest.cpp which can perform 3 tests
according to the setting of variable 'test'
	1. BLOCK_TEST - basic read / write of blocks
	2. FILE_TEST - writes a series of CASTOR files and reads
a random one
	3. RAO_TEST - performs a RAO query for a series of files
given in the filename specified in argv[1]. The file format should
respect the above mentioned order.
Signed-off-by: Cristina Moraru <cristina-gabriela.moraru@cern.ch>

This uncovered several failures to fetch again after relocking objects in unit tests (fixed as well).

Added many conditional printouts in unit tests. Those printouts are controlled by #defines in a central file.

The cta-frontend and cta-taped rpms now create /var/log/cta

Packaged cta-taped.sysconfig and cta-taped.service

Packaged cta-frontend.logrotate and cta-taped.logrotate

Packaged the man page of cta-taped

Revert "Revert "Removed 'Do nothing' logic from cta::server::Daemon which unwantedly kicks in if systemd is used""

This reverts commit 2d27ddb0.

Reverting the revert because nothing changed.  The GitLab CI still
does not succeeed in running the "init" pod.  The commit I made
and then reverted appears to have nothing to do with the problems
of the GitLab CI.

Revert "Removed 'Do nothing' logic from cta::server::Daemon which unwantedly kicks in if systemd is used"

This reverts commit 4c7439cf.

The current pipeline in the GitLab CI keeps failing to complete
the "init" pod's work.  The same Docker image is used on
stevedevctai.cern.ch to successfully run systest.sh -n ctatest.

The GitLab CI does not provide any logs from the "init" pod and
therefore cannot be debugged.

This revert is a desperate attempt at fixing ithe problem.  If it
does work then it means the GitLab CI is benefiting from cta-taped
remaining as the root user.

Fixed calls to promise::get_future() after possible access form other thread. They are now guaranteed to happen before.
Added helgrind annotations for promise based synchronisation.
Added macros enabling helgrind annotations for shared_ptr.
Added suppression for shared_ptr used inside other standard lib object and not covered by the previous macros.
Added unit test for lower level .
Added suppressions for reported race conditions in Rados library.
Review heavily MemArchiveQueue and fixed missing commit in object store, leading to potentially orphaned objects.
Enabled formerly disabled test as it is now fast enough.

Changed user stage:st to cta:cta

cta-taped now logs the user and group that it is setting for the
current process.  For example:

May 18 16:54:13 itdssbuild01 cta-taped: <158>2017-05-18T16:54:13.402884+02:00 cta-taped[17210]: LVL="Info" TID="17210" MSG="Setting user name and group name of current process" userName="stage" groupName="st"

Add publish_tagged_rpm and needed helper derived from https://gitlab.cern.ch/ci-tools/ci-web-deployer as we need to run the update_repo.sh hook after the file transfert.

Adding cta_tagged_rpm stage. CTA_RELEASE and CTA_VERSION are not exported as is to avoid overriding environment variables used by cmake. Therefore I am using TAG_VERSION and TAG_RELEASE.