TrigConfReadWrite application to return FATAL if metadata write fails (ATR-16103)

When TrigConfReadWrite is unable to complete populating in-file metadata it
typically aborts in such a way that any reco job in which it is running does
not register the failure. This can then cause confusing crashes in later jobs,
as demonstrated in ATR-16121. This change will cause the tool to issue a 'FATAL'
to the log of the original job, meaning processing will stop at the point of
the original error.

Trigger/TrigConfiguration/TrigConfStorage/src/test/ReadWrite.cxx

@@ -678,10 +678,14 @@ int main( int argc, char* argv[] ) {
       
       if(ctpc)
          coolWriter->writeL1Payload(runNr, *ctpc);
-      
-      if(hltFrame)
-         coolWriter->writeHLTPayload(runNr, *hltFrame, configSource);
-      
+      try{
+	if(hltFrame)
+	  coolWriter->writeHLTPayload(runNr, *hltFrame, configSource);
+      }   
+      catch(cool::StorageTypeStringTooLong e){
+	log << "FATAL: Unable to write data to COOL";
+	exit(1);
+      }
        if(mck)
          coolWriter->writeMCKPayload(runNr, mck, release, info);
    }