This timeout actually covers a grace period for draining the metadata to central storage.
Bumped it up from 5 seconds to 5 minutes.

Refactoring layers to limit their number and catch possible errors using && instead of ; between commands

The previous case, keeping a reference created a race condition as 2 threads would
use the same logContext.

Added mechanism to make sure the ArchiveQueue lock is released only after all requests
have had their ownership updated.

AgentReference::queueAndExecuteAction() missed the waiting on the promise.
Added log when a non-owned job is popped from an archive queue.

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

The timeout is now set to zero in unit tests.

AgentReference::{addTo|RemoveFrom}Ownership() are used instead.
Fixed typo in function name.
Added missing lock in AgentReference::queueAndExecuteAction().

The queue is housed in the AgentReference class. It currently covers the add to ownership
and remove from ownership operations. This queued system guarantees in-order execution
of operations.

Adding Database and Objectstore deletion feature: I merged the wrong commit when moving cta-orchestration in CTA repo.

Using lower case only for configmap keys as Eric had a problem with upper case with the same kubectl binary... Will be fine for everyone this way.

Work for issue #65 EOS+CTA interface definition and implementation

Those queues will hold in memory the addition of the archive requests from several threads
and them all in one go, in order to limit contention and round trips on the object store.

Work for issue #65 EOS+CTA interface definition and implementation

Waiting for library configuration. If missing it leads to failed test: no drive tape or library available...