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

The status of the repack request is updated throughout all its lifecycle (Pending, ToExpand, Starting, Running, Complete or failed)

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.

The retrieve requests now carry all the information necessary to create the archive jobs.
Retrive requests carry an isRepack boolean. The distinction between repack and non-repack behaviour
is pushed as low as possible in the api (in the object store) so that client code can be more
generic. For the same reason, the
The expand repack mode (re-creation of missing tape files) is not supported yet.
Changed the represenation of copy numbers to uint32 (as this is the smalled number supported but protocol buffers).
Added ArchiveRoute::StorageClassMap and ArchiveRoute::FullMap to store archive routing in memory.
Added repack buffer base URL support, and mechanism to compute temporary copy location in disk cache.
Fixed bug in ObjectOps<>::asyncInsert();
Inplemented the path generation for repack disk storage (<BaseURL>/<VID>/<FSeq (09%d)>).

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.

Queueing of Archive Jobs is done and unit tested
Queueing of Retrieve Requests is not completely done yet

Removed the "User" message from the cta.proto (duplication of UserIdentity message)

Repack RetrieveRequest reported as success after mount and retrieve successful (expandRepackRequest)

Added MEDIA_TYPE and VENDOR columns to TAPE table and upgraded xrootd-ssi-protobuf-interface to v0.29

This promotion is controlled so that only a limited number a requests
are in the
state ToExpand or Starting at any point in time. This ensures both the
availabality
of repack file requests to system while preventing an explosion of file
level requests.

Created a one-round popping from the container (algorithms) with status
switching.
  - Used for repack requests switching from pendig to to expand

Added ElementStatus to algorithms.

Implemented promotion interface in Scheduler and OstoreDb. The actual
decision is taken at
the Scheduler level. The function itself is called by the
RepackRequestManager.

Promotion is tested in a unit test.

Various code maintenance:
Switched to "using"-based constructor inheritance.
Fixed privacy of function in cta::range.

Merged RepackInfo and RepackType.
Simplifed RepackInfo to what is currently implemented.
Implmented repack related dumps.

Added partial support for repack queueing in scheduler database,
scheduler and CLI.

Done