- BROKEN tape cannot be queued for repack
- DISABLED tape cannot be queued for repack if the --disabledtape flag has not been provided by the user
- NOT FULL tape cannot be queued for repack

[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

- ADD NOT NULL CONSTRAINT TO VIRTUAL_ORGANIZATION.READ_MAX_DRIVES
- ADD NOT NULL CONSTRAINT TO VIRTUAL_ORGANIZATION.WRITE_MAX_DRIVES
- removed the MOUNT_POLICY.MAX_DRIVES_ALLOWED column
- Migration scripts

- NOT NULL CONSTRAINT on TAPE_STATE
- NOT NULL CONSTRAINT on STATE_UPDATE_TIME
- NOT NULL CONSTRAINT on STATE_MODIFIED_BY
- Removed the columns TAPE.IS_DISABLED and TAPE.IS_READ_ONLY and their
  constraints

- SUPERSEDED_BY_VID removed
- SUPERSEDED_BY_FSEQ removed
- RAO associated columns removed
- ARCHIVE_FILE_RECYCLE_BIN removed
- TAPE_FILE_RECYCLE_BIN removed
- Migration scripts

Increase the minRequestAge in the getNextMountWithArchiveForUserAndArchiveForRepackShouldReturnBothMountsArchiveMinRequestAge test

Activated stdout output for getNextMountWithArchiveForUserAndArchiveForRepackShouldReturnBothMountsArchiveMinRequestAge test

getNextMountWithArchiveForUserAndArchiveForRepackShouldReturnBothMountsArchiveMinRequestAge
modified to wait 2 seconds instead of one after having changed the min
request age

- BlockId and CopyNb were swapped when superseded files moved to the
  recycle bin
- If a tape is disabled without any user comment, an default comment is
  set

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

[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