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

[migration] Added the two columns READ_MAX_DRIVES and WRITE_MAX_DRIVES to the VIRTUAL_ORGANIZATION table in the liquibase migration scripts

[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

- Removed the counting of the readonly tapes as they don't exist
- Count the ACTIVE tapes instead of not disabled ones
- Repack disabled tape system test now undisables the tape after having
  reclaimed it

This revert is due to the fact that we will probably not put the
maxdrivesallowed in the mount policy object. We will put it in the
TAPE_POOL table and in the VIRTUAL_ORGANIZATION table

This reverts commit f48c6cc48eaa9ab9e77fff5a4537a7a4641896b6.

[catalogue] Created a catalogue::CreateMountPolicyAttributes object and added the maxDrivesAllowedPerVo field

[catalogue] Added the tape states to the catalogue::getTapes() methods + TapeSearchCriteria + unit tests + refactoring

[catalogue] Added the tape lifecycle columns in the database + the method to modify the state of the tape

[cta-admin] Implemented cta-admin recycletf ls [--vid] [--fxid] to list content of the FILE_RECYCLE_LOG table

[catalogue] Storage class deletion modified to check if there are files on the FILE_RECYCLE_LOG table before deleting the storage class

[catalogue] TAPE_FILE.SUPERSEDED_BY_VID and TAPE_FILE.SUPERSEDED_BY_FSEQ are not used in any query anymore