Revert "Added oracle-instantclient-tnsnames.ora which was implicitly being installed by oracle-instantclient19.3-meta which we no longer install"

This reverts commit 8083df2a.

Added oracle-instantclient-tnsnames.ora which was implicitly being installed by oracle-instantclient19.3-meta which we no longer install

This reverts commit edf98416.

docker/ctafrontend/cc7/opt/run/bin/init.sh now installs the standard oracle-instantclient19.3-sqlplus rpm instead of the CERN version

Add standalone command line tool cta-tape-label.

Command mount, label, umount the tape pointed by VID option. Tape drive
and library parameters used from /etc/cta/TPCONFIG file and catalogue
parameters from /etc/cta/cta-catalogue.conf.
To be labelled the tape must be present in the catalogue and must be
empty.
By default the tool labels the tape with enabled logical block protection
if drive supports such mode. For non-blank tapes command checks previous tape
label and label only if the old label is the same or match to the label in the
command line oldLabel option. To skip label checks for non-blank tapes --force
option could be used.

Flushing stdout and sending ERROR messages to stdout as redirection would be applied to stdbuff command

the kubernetes CI namespace and externally.
More in README_postgres.md

removing replace-str option as -L just concatenates args after the replace-str place holder. toto is not a valid rados object which prevents the objectstore cleanup.

The installation in the buildtree environment is not useful as all is pre-installed in the image.

Purging Oracle DB recycle bin in init, otherwise CI DB size explodes because of the recycle bin content.

Performing 100 rm in parallel for rados, this should not be painful as those synchronous rm are mostly waiting

added a /CANSTART file so that eos waits for all keys to be OK before starting.
/bin/sh -> /bin/bash to allow function names with `-`...
yum and yum-config-manager overridden when in BUILDTREE environment
ctafrontend not booting needs further work

cta/CTA#87 cta-catalogue-delete-all-data and cta-catalogue-schema-drop should require interactive confirmation

Removed the now redundant locking commands for the catalogue schema.
These commands were made redundant when the cta-catalogue-schema-drop
command was made interactive.

cta/CTA#87 cta-catalogue-delete-all-data and cta-catalogue-schema-drop should require interactive confirmation

Made the cta-catalogue-schema-drop command interactive

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

Cleaning up run scripts for containers: going along Dockerfile and in /opt/run/bin: /shared still available for local scripts developments.