Added ability to specify the TPC region name prefix

[bieryAtFnal]

As requested by Florian and others working in the control room.

Please note that this changes does not affect the detector Group name in the HDF5 file. That will remain "TPC". It only affect the level below that, where "APA" can be changed to "CRP", for example.

GROUP "TriggerRecord00032" {
      GROUP "TPC" {
         GROUP "CRP000" {
            DATASET "Link00" {
               DATATYPE  H5T_STD_I8LE
               DATASPACE  SIMPLE { ( 37200, 1 ) / ( 37200, 1 ) }
            }
            DATASET "Link01" {
               DATATYPE  H5T_STD_I8LE
               DATASPACE  SIMPLE { ( 37200, 1 ) / ( 37200, 1 ) }
            }
         }
      }
      DATASET "TriggerRecordHeader" {
         DATATYPE  H5T_STD_I8LE
         DATASPACE  SIMPLE { ( 128, 1 ) / ( 128, 1 ) }
      }
   }

[bieryAtFnal]

That is my assumption, too. It's also a little worrisome that these changes don't play very well with TP generation, which is still set to use a region name prefix of TP_APA. My sense is that these shortcomings are OK, though, because we are not mixing VD and HD data at NP04/02 and there are only a small number of detector components in either case.

[alessandrothea]

Let's say we won't mix APA and CRP until 2.8.3 😉 PhotoDetectors, on the other hand... we shall see. I think this is fine for now, to the extent that allows us to run both coldboxes without having to modify json files by hand.