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)

Add youngestjobcreationtime to archive and retrieve queues in the
objectstore. The change is backwards compatible, as the new field is
optional and with a default value of 0.

The field is updated everywhere in the code where oldestjobcreationtime
is also updated. The value is printed per queue using cta-admin sq.

When StdoutLogger is used in combination with systemd, then header
becomes redundant.

Signed-off-by: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>

* Add clientHost to the cta::common::dataStructures::SecurityIdentity struct, defining the machine the cta command was submitted from
* cta::comon::dataStructures::SecurityIdentity::host now represents the frontend machine the commands were executed on, and is set by the server

Add create/deleteDriveConfig methods and rename input values in SourcedParameter to avoid shadowing the methods

Objectstore GC Repack unit tests rely on a specific string in an exception message.

Refactors XrootCl.cpp to sanitise value returned by
`XrdCl::XRootDStatus::ToStr()`

[cta-admin] Cleaned cta-admin deprecated methods and remove fields for cta-admin --json output of the commands that were modified by CTA v4.0

- cta-admin --json sq showqueues does not show maxdrives anymore but read/write max drives
- cta-admin --json showqueues does not display the next mounts, empty tapes, readonly tapes and disabled tapes anymore
- cta-admin --json mountpolicy ls does not display the old maxDrivesAllowed parameter anymore
- cta-admin --json tapefile ls does not display supersededByVid and supersededByFseq anymore

- next mounts was introduced to anticipate the drive dedication
  implementation. As it is not implemented, it is removed from the cta-admin sq output

Catalogue::getCachedVirtualOrganizationByTapepool() + VO added to the DriveState object + VO and read/write max drives added to the getQueuesAndMountSummaries method

- Objectstore definition modified : there is no maxDrivesAllowed item
  anymore

[scheduler] The scheduling now takes the VO readMaxDrives and writeMaxDrives parameters to trigger a mount or not

[catalogue] Added the MAX_DRIVES_ALLOWED_FOR_READ and MAX_DRIVES_ALLOWED_FOR_WRITE columns in the VIRTUAL_ORGANIZATION table

- Modified the RdbmsCatalogue::createVirtualOrganization() method
- Added the RdbmsCatalogue::modifyVirtualOrganizationMaxDrivesAllowedForRead() method
- Added the RdbmsCatalogue::modifyVirtualOrganizationMaxDrivesAllowedForWrite() method