Dropped the TAPE_FILE_VID_ARCH_FILE_ID_UN constraint

This constraint prevents a tape server from writing the same file
more than once to the same tape.  We should actually allow this
to happen so that we can tolerate the pathological case of a
cta-taped daemon crashing immediately after inserting a row into
the TAPE_FILE table and before updating the object store.

catalogue/catalogue_common_schema.sql

@@ -190,8 +190,7 @@ CREATE TABLE TAPE_FILE(
     REFERENCES TAPE(VID),
   CONSTRAINT TAPE_FILE_ARCHIVE_FILE_FK FOREIGN KEY(ARCHIVE_FILE_ID)
     REFERENCES ARCHIVE_FILE(ARCHIVE_FILE_ID),
-  CONSTRAINT TAPE_FILE_VID_BLOCK_ID_UN UNIQUE(VID, BLOCK_ID),
-  CONSTRAINT TAPE_FILE_VID_ARCH_FILE_ID_UN UNIQUE(VID, ARCHIVE_FILE_ID)
+  CONSTRAINT TAPE_FILE_VID_BLOCK_ID_UN UNIQUE(VID, BLOCK_ID)
 );
 INSERT INTO CTA_CATALOGUE(
   SCHEMA_VERSION_MAJOR,