- XRootD/SSI/Protobuf errors or CTA Exceptions return error code 1
  (something went wrong with communication or in the frontend)

- User errors return error code 2 (user specified an invalid drive,
  vid, etc.)

- If text output, print error message on stderr and exit with code 2

- If --json output, print error message on stderr, print empty JSON
  array [] on stdout, and exit with code 2

CreateAllSchemasCppFile.sh now sorts the directories of the schema versions so that the map of schemas is created

Adapted the cta-catalogue-schema-verify tool to deal with the SchemaVersion object and displaying a warning
in case of running database upgrade

Added CATALOGUE_STATUS_CONTENT_CK constraint checking in Postgres and MySQL schemas

Added SchemaMetadataGetter class in order to filter the database-metadata content returned by the SQLite schema we use to check the Catalogue database
Example: for Postgres, we cannot get the NOT NULL constraint names, so we filter these constraint names from the SQLite database in order to
not display that the Postgres catalogue has missing NOT NULL constraints

ARCHIVE_ROUTE_COPY_NB_GT_ZERO renamed to ARCHIVE_ROUTE_COPY_NB_GT_ZERO_CK
LOGICAL_LIBRARY_LLN renamed to LOGICAL_LIBRARY_LLN_UN
TAPE_FILE_COPY_NB_GT_ZERO renamed to TAPE_FILE_COPY_NB_GT_0_CK
USAGESTATS_GID_TS renamed to USAGESTATS_GID_TS_PK

Renamed constraint CTA_CATALOGUE_STATUS_CONTENT_CK to CATALOGUE_STATUS_CONTENT_CK to have a less than 30 characters constraint name

Removed SQLite migration directory

Corrected the MapSqlStatementsReader::getStatements() method so that it throws an exception if the schema corresponding to a version does not exist

Reverted the renaming of the INDEX TEMP_T_F_I_B_ARCHIVE_FILE_ID_I, will be changed in the version 1.1 of the schema

All indexes have now the same names, cta-catalogue-schema-verify now checks for user created indexes

Added a class SchemaChecker that has the responsiblity of checking :
- the schema against the .sql defined in the SCHEMA_VERSION/xxx_catalogue_schema.sql
- the presence of PARALLEL tables in ORACLE (not implemented yet)

A directory is created regarding the version of the catalogue, the xxx_catalogue_schema.sql is inserted in it at each modification of the schema by the user