Remove activity fair scheduling logic
The support for activity fair scheduling has never been used in production. It is not tested, unfinished and it is blocking the upgrade to EOS version 4.8.67.
The only use of activities in CTA should be for the ActivityMountRules implemented for https://gitlab.cern.ch/cta/CTA/-/issues/1026
This would ideally be done before upgrading to EOS 4.8.67. Currently it is not expected that any jobs with activities are in the queues, so we can change the objectstore schema that touches in activities in a way that is not backwards compatible.
We should also remove the activity weight field from the drive states.
While this is not on the critical path, it would still be nice to do if it is not too complicated.
Edited by Miguel Barros