ADD: Hardware threshold files from unit-level data

[fhagemann]

Needed by #190, addressing issue #195:

Based on the threshold finding app, @JarredMRoberts determined the hardware threshold files and uploaded them to Google Drive: https://drive.google.com/drive/folders/1FN4fp0_imv-opuJHoKn1N3DPwUUPe38A?usp=sharing

In this PR, we're adding the files for the individual flight detectors to resource/calibration/COSISMEX/unit, and a combined file containing all 16 flight detectors to resource/calibration/COSISMEX/payload.

I made some changes compared to the files that were on Google Drive:

• renamed the files to follow the naming convention used for the simulated depth splines
• added a first column STRIP_ID determined from the strip map to follow the format of resource/dee/dummy_hardware_thresholds.csv (which follows the format also of the average fast/slow threshold files that we determine in unit-level testing)

I'm opening as a draft for now, because I haven't tried running the code in #190 using these threshold files.
Will mark this as "ready for review" once I have tested this.

[fhagemann]

So, I ran nuclearizer using a cosima simulation for 542-1 on the STTC, and using the 542-1 hardware threshold file.
The energy histogram when applying the energy calibration looks reasonable (in the sense that it seems to be adding a noise peak):

Will test this more thoroughly tomorrow, but this looks promising (at least for 542-1)

[fhagemann]

Browsing through different strips (I did this for 542-1) seems to yield reasonable results in the DEE:

[ckierans]

Looks good, @fhagemann !