Catalogue classes now propagate exception::LostDatabaseConnection

Added CatalogueRetryWrapper.hpp

Fixed various bugs detected through it.

Now copies keytab between pods and changes ownership/permissions atomically

This reverts commit fc001693.

The CI was incorrectly failing.  There was nothing wrong with
the original commit that made the Catalogue class a pure
interface.

This reverts commit abe44e72.

CTA_StorageClass was hard coded. In this version it is read from the
extended attribute.

The workflow now includes the endpoint, which includes the Kubernetes namespace that the pod is
running in.

cta-cli.sss.keytab is deprecated. CTA Frontend now uses
/etc/cta/eos.sss.keytab, which should contain one SSS key per EOS
instance (only one in the case of CI).

This version of eos-server includes the WFE implementation for CLOSEW
(default and CTA_Archived), ARCHIVED, PREPARE and DELETE. The bash
scripts are no longer necessary.

Moved maxTriesToConnect parameter to CatalogueFactory::create().

Corrected handling of LostDatabaseConnection exceptions within OracleCatalogue

OracleCatalogue::deleteArchiveFileByDiskFileId()  should re-connect to database if connection lost.

OracleCatalogue::deleteArchiveFile()  should re-connect to database if connection lost.

Refactored retryOnLostConnection() from OracleCatalogue and RdbmsCatalogue