The retrieve request now gets properly queued in case of retrieve error.
The errors are counted and the request gets deleted eventually.
A new field was added to the retrive request in object store. This commit
will fail on upgrade if there are retrieve requests still queued at update time.
Cleaned up some unused structures in cta.proto
Minor modifications to ArchiveJobs.

Converted all bytes to Mbytes. Removed extra space in the output.
Reordered fields.

This is a stop gap solution while we wait for efficient archive/retrieve reporting.

This affects only unit tests as taped already relied on getNextJobBatch().

As rados re-creates an object when trying to lock it, we tested for presence before locking.
This is racy as object could be deleted in the mean time.
Instead, we now lock blindly and delete the object if we find it having a zero-size.
As we own the lock, this is safe.

This problem led to issues in garbage colector, where agent gets polled while it could disappear.

This fixes frontend failing to start on file permission error.

Set default to 8k as seen in this documentation:
http://www.rsyslog.com/doc/v8-stable/configuration/global/index.html.

Added the vid in the name of the retrieve queue object.

Also fixed flaws in the cache update logic.

Some further adaptation was needed on the templates.

It is now known as ostoredb::MemQueue<ArchiveRequest, ArchiveQueue>. This is in preparation of the reuse of the code
for ostoredb::MemQueueu<RetrieveRequest, RetrieveQueue>.

their namespace.
According to
https://kubernetes.io/docs/concepts/configuration/secret/#creating-a-secret-using-kubectl-create-secret:
```
Secret API objects reside in a namespace. They can only be referenced by
pods in that same namespace.
```

This allows to solve the recurrent docker login issue by passing the
credentials to kubernetes as a secret.
Indeed docker login credentials are valid for 3 months then it is over.
We just need to pass the `ctareg` service account credentials in the
`ctaregsecrets` and we are done.
In addition `imagePullSecrets` works at the full cluster level as each
kubelet needs the registry credentials to pull its own image.
If `ctaregsecret` secret does not exists, kubernetes is perfectly fine
with that and uses the default authentication. This means that there is
no need to define this secret (which is useless in the buildtree
environment).

Changed the default behavior of DummyCatalogue so unit tests keep passing.
Adapted SchedulerDatabase API.

Added tapepool information from the catalog in
Scheduler::getQueuesAndMountSummaries.

Created a unit test for RetrieveRequest garbage collection.
Created a RetrieveQueue::addJobIfNecessary function.
Fixed various bugs in RetrieveRequest::garbageCollect.
Added basic functionnality to DummyCatalogue for GC unit tests.
Cleaned up interace of RetrieveRequest for functions that are never used.
Implemented missing function in RootEntry.
Homogenized capitalisation of object names.
Added support for RetrieveRequest in cta-objectstore-collect-orphaned-object.

Added a tape queue and status cache update function in objectstore::Helpers.

In order to be efficient, the data (tape status and queue sizes) is cached in memory.
This function needed access to the catalogue (where the tape status is located).
This in turn required passing the catalogue object to:
 - The garbage colletion functions for all object types.
 - The garbage collector object now keeps a reference to the catalogue.
 - The path to the catalogue credential file should now be passed to cta-objectstore-collect-orphaned-object
 - The OStoreDB also needs a reference to the catalogue in order to queue retrive requests.

 The garbage collection member function are now also being passed a log context, so the requirement for better
 log of object fate can also be fulfilled later. This in turn required the passing of a logger object to
 the object store and relative helper classes.

 Finally, a dummy catalogue class has been created to be used in unit tests.

sort out tests that failed because of EOS instance

updating EOS to 4.1.25-20170717140631git057a3ea, versionlocking all the packages from the official repo as some disappeared (eos-4.1.25... is no more).

This commit does two things.  Firstly it puts back the call from:

    XrdCtaFile::xCom_deletearchive()

to:

    Scheduler::deleteArchive()

Secondly it moves the reponsibility of logging the
"Archive File Deleted" message from the CTA front-end (XrdCtaFile)
to the CTA catalogue.

Please note that Scheduler::deleteArchive() still does not call
SchedulerDatabase::deleteArchiveRequest().

This is a TEMPORARY modification to the  CTA front end.

When an "eos rm" command is executed the xCom_deletearchive()
method of the CTA front is called.  Before this commit the
mthod would try to removed the archive file from both the
object store and the CTA catalogue.  This took more than 15
seconds to complete under som ecircumstances.  This commit
removes the call to the object store.

Please note that this commit will causes a leak in archive
files.  If a file is "in-flight" and therefore has not yet
been written to tape and recorded in the CTA catalogue
then a call to "eos rm" will do nothing and the file will
eventually appear in the CTA catalogue when it is written
to tape.  The file will therefore NOT be in the EOS
namespace but it WILL be in the CTA catalogue.