Remove catalogue version 5.0 from CTA and move backwards compatible changes to catalogue version 4.6

Add a RESERVATION_SESSION_ID column to the drive table.

When releasing disk space, only do so if the mount id is equal to the
reservation session id

Make cta-admin --json sq show the mount policy with highest priority and the
mount policy with lowest request age for each queue

New catalogue table and respective cta-admin diskinstance and
cta-admin diskinstancespace commands

Refactor the RecallTaskInjector to limit the number of tasks passed
at once to the TapeReadSingleThread for a tape with RAO and to reserve
disk space in smaller batchs

In every call of RecallTaskInjector::synchronousFetch the injector
will try to pop jobs from the queue so that it holds an ammount of
work equal to the limit of files or bytes imposed by the RAO
implementation or by the value given by the
BulkRequestRecallMaxBytes and BulkRequestRecallMaxFiles config
options in /etc/cta/cta-taped.conf.

In every call of RecallTaskInjector::injectBulkRecalls the
RecallTaskInjector will inject a set of tasks limited by the
BulkRequestRecallMaxBytes and BulkRequestRecallMaxFiles config
options in /etc/cta/cta-taped.conf to the TapeReadSingleThread
and DiskWriteThreadPool.

The disk space reservation is done once for every job batch (instead of
all the disk space being reserved when the jobs are popped)

This prevents tapeservers with RAO from reserving a large amount
of the disk buffer upfront, which would cause the buffer to fill quickly
by a few drives, which cannot fill it fast enough

Activity Mount Rules associate a Mount Policy to an activity regex.

When recalling a file, the users can specify an activity (i.e. by using
filepath?activity=x). If specified, this activity will be used to select
a matching activity mount rule, if one exists. If more than one Activity
Mount Rule matches the activity, the one with highest retrieve priority
will be chosen.

Acitivity Mount Rules take precedence over Requester Mount Rules.

Remove all the code associated to the activity weight fair share
scheduling feature:

- Remove catalogue functions interacting with the ACTIVITY_WEIGHTS table
- Remove code related to activity weights from the scheduler.
- Deprecate and mark as optional objectstore schema fields for activity
  weights (shcema should be backwards and forwards compatible).
- Store only activity information in the drive state. In the catalogue
  methods, default the weight values to 1.0 (avoids having to perform a
backwards incompatible catalogue upgrade)