Added a second XrdSecDEBUG=1 to the workflow action of event sys.workflow.closew.default within the eoscta pod

Added XrdSecDEBUG=1 to the workflow action of event sys.workflow.closew.default within the eoscta pod

We must run against the same version of Rados we compiled against. Now enforced in
RPM.

Also enforcing version matching between cta-lib and dependant packages.

Also added an access after each context in order serialise their creations.
Logs should at least permit better understanding of crashes.

/etc/sysconfig/cta-rmcd should have noreplace as well, otherwise a production package update can kill the media changer on all tapeservers

The rados operations now round-robin on the contexts to spread the load.
Modified the not yet used thread pool of BackendRados so it does not have its own context
anymore.

Fixes failure mode where sizeof(uint32_t) + buflen exactly equals the
buffer size, and m_split_buflen had been set to a non-zero value in a
previous iteration.

Both tapeFile::ReadSession and tapeFile::WriteSession start by
reading VOL1 by calling Drive::readBlock() with a block of 84
bytes even though Logical Block Protection (LBP) is turned off
at this early stage of a session.  With LBP turned off, a drive
will only return the exact record being read and wil not add 4
CRC bytes at the end.  This means the drive will always return
80 bytes.

Both tapeFile::ReadSession and tapeFile::WriteSessioas called
Drive::readBlock() with a block of 84 bytes in order to work
with an "in-house" version of mhvtl that tried to support LBP.
Unfortunately the behaviour of this special version of mhvtl
was incorrect because it would 84 bytes when LBP was disabled.

The "in-house" version of mhvtl trying to support LBP is no
longer used with CASTOR.  This commit therefore simplfies the
CASTOR code by replacing Drive::readBlock() with
Drive::readExactBlock and by removing the conditional logic
that dealt with the existance of an 84 byte VOL1 label in the
presence of the "in-house" version of mhvtl.

Prepare was failing in client_ar.sh because of a typo in KrB5CCNAME, adding -s to prepare as by xrootd definition we are staging files to disk and not discovering them.

moment and won't be used in production (egroups).