Regex based on cta::utils::Regex (regexec POSIX regex function)

Examples of usage:
  cta drive up .
  cta drive down ^VDSTK
  cta drive down ..STK.[0-1] -f

if they not set for the cta-objectstore-... commands.

If these parameters are not set the commands will try values from the
/etc/cta/cta-frontend.conf and /etc/cta/cta_catalogue_db.conf

Also added some lockfree fetches.

The reponse rate of the CTA catalogue to "eos rm"
commands was too slow.  The response rate was
around 20Hz when using the CTA/EOS production
database configured with 10 database connections.
The rate has now been increased to 30Hz by adding
the TAPE_FILE_ARCHIVE_FILE_ID_FK index.

We can now get data from a different source (/dev/zero or a file). This helps test where mhvtl space is tight
(so compression can be efficient).

Ported improvements of Helpers::getLockedAndFetchedQueue<ArchiveQueue>() to Helpers::getLockedAndFetchedQueue<RetrieveQueue>().

Also used lockfree in initial access to root.

This reverts commit 7388bd57.

The 'SELECT FOR UPDATE' was not the bottle neck.  I am putting it
back for now.

session finished" cta-taped log messages always be on the end.

updating wfe.ntx to 10 and wfe.interval to 1 as 3 was way too low (1 is to match preproduction number of wfe.interval).

To activate this option run CMake with:

$ cmake -DBUILD_XROOT_SSI=1 ../CTA

Especially, in OStoreDB::fetchMountInfo(), some operations were not lock free where they should have been.

Proceed all successful reports asynchronously and periodically check
and clear statuses if they have finished.
In the end of session do the check/flush for all reports in the
successful reports queue.

Switch from synchronous rados remove to async aio_remove in
case of zero size object in BackendRados::AsyncUpdater

As those fuctions are usually called in a tight loop at the end of the session or in the garbage collector,
they tend to unlock and relock the queues immediately, and sitting on the lock for a long time in practice.
The added sleep will increase the odds of other processing slipping in between the unlock and the lock.

The ping() and queueRetrieve() timings are of interest, so commit now.
The rest of the timings will follow.