dropped the possibility to log to DLF from within the DB without autocommit. This was dangerous as it could led to blocking the core service for logging purposes

Improved version of the upgrade script. Almost final version but needs testing + expansion of the PL/SQL included via the @ statement

shorter, in order to limit the impact of cases like the one in
SR #127670: disk2disk copy for old/obsolete file succeeds after a namespace truncate

Cleaned up the logging code in the tape gateway as all per-file logging responsibility was taken over by the PL/SQL code.
Updated gateway tests for 2.1.13 (still under construction).

trigger statement with an ON SCHEMA clause.

creation script was trying to be create on the non-existant table named Tape:

    UN_Tape_VIDSideTpMode
    NN_Tape_lastVdqmPingTime

statement was in the wrong place and was causing the following error message
when trying to create the stager schema:

			   nbRetries INTEGER CONSTRAINT NN_MigrationJob_nbRetries NOT NULL DEFAULT 0,
                                                                                           *
ERROR at line 9:
ORA-00907: missing right parenthesis

I have now moved the DEFAULT 0 clause to immediately after the column type.
There are other problems with the stager creation script that still need to be
fixed.  I hope it is only one more problem and not many.

as all its calls are anyway executed by the tapegatewayd.

to the schema this time after Sebastien's big refactoring,
only some improvements in the logging (now both migrations and recalls
have a request UUID for each bulk update).

the error-code of EIO if there is a problem opening the file.

    castor::common::CastorConfiguration

It would appear that there was two possible design choices, first implement the
class as a map of maps or implement it an object containing a map of a map.
Unfortunately both design choices appear to have been implemented which does
not really work.

override the default location of the CASTOR configuration file.  This feature
is used for testing this part of the code.

    castor::common::CastorConfiguration

two messages have been removed from the tapegateway protocol:

    BaseFileInfo
    EndNotificationFileErrorReport

message no longer exists in the tapegateway TCP/IP application-protocol.

getconfent.c has been replaced by getconfent.cpp

marshalling of arrays or custom types over a db link, hence temporary
tables are used to transfer the data and read back the results.
Also introduced a serrno PL/SQL package in both the NS and Stager
databases.
Adapted the OCCI interface to match the PL/SQL procedure for migration,
still some modifications to be done (the bulk methods don't return anything)
prior to start testing.

- A new Nameserver PL/SQL API
- PL/SQL procedures for the tapegateway to request and commit multiple files in one go.
Other schema changes:
- The tapeGatewayRequestId is gone from MigrationJob and MigrationMount,
  and it has been replaced by the mountTransactionId, aka the VDQM transaction id,
  with a PK-FK constraint.
- The MIGRATIONJOB_RETRY status has been dropped together with the python policies
  handling, that is now fully PL/SQL like for recalls.
The schema version has been moved to 2_1_13_0.

changes of the Nameserver schema as it was prior to 2.1.9-3.

(re)created migrationJob to bypass the throttling policies.

This involved moving the definition of basic exceptions to the libcastorcommon and thus adding dependencies to this library in a couple of places that depended only on libcastorclient