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)

- rpm spec file
- ci build/test containers

In the case the archive has no active files, distinguish between

- no ACTIVE tape with copy and at LEAST one non BROKEN copy
- All copies on BROKEN tapes
- No entry in CTA catalogue

And suppresses two false positive warnings in templated classes

Restoring deleted files implies restoring them in the eos namespace and
in the cta catalogue. The command has no atomicity guarantees, a file
may be restored in the eos namespace but the restoring in the cta
catalogue may fail.

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.

Not running cppcheck analysis on tag pipelines as these already ran on the corresponding commit pipeline