These commands are not implemented so I have removed them from the cta-admin
interface.

Renamed the database constraint TAPE_FILE_SS_VID_FSEQ to TAPE_FILE_SS_VID_FSEQ_FK so that it follows CTA naming convention

Fixed.

Moreover, the PL/SQL code for the CTA catalogue is temporarily
moved out of the catalogue folder as it requires some schema
changes that are still work in progress in a dev branch. Until
then, all migration code is evolved in the migration/ folder.

References:
https://gitlab.cern.ch/cta/CTA/issues/479 (on the CTA side)
Jira: CASTOR-5526: support the migration to CTA (on the CASTOR side)

The latter won't be updated further, all required code will
be committed here and gitlab tickets will be updated accordingly.

Corrected cta-admin af ls command so that it fills the superseded vid and superseded columns in the result

Replaced the map of tape files with a list as the assumption that we have one copy per copyNb is no more valid with repack.

Added a check while mounting a tape for writing : if some tape files located in the writing tape are not superseded by others,
the write session will fail.

Note: The test CatalogueTest.exist_non_superseded_files_after_fseq is supposed to fail.

Harmonized the copyNb type to uint32_t
Corrected a bug in RetrieveQueue::getContainerSummary() --> After insertion in the queue, the number of files and bytes added were equal to 0.

This commit works towards issue cta/CTA#436.

CatalogueTest now asserts new archive file identifiers are unique as opposed to strictly incrementing sequentially by 1

Woah!  Got carried away with const.  This commit Removes the const
qualifier from the ArchiveFileItor::next() method because next()
modifies the iterator.

To loop through an ArchiveFileItor:

  auto itor = catalogue.getArchiveFilesForRepackItor(vid, startFSeq);
  while(itor.hasMore()) {
    const auto archiveFile = itor.next();
    // Do something with archiveFile
  }