Fix special thresholds in fax file by pulling from CMT

[JoranAngevaare]

Currently, we have these thresholds in the fax-config file. Ideally, we pull this from CMT to avoid discrepancies between the simulated and processed data.

This adds a very tiny bit to the bias (see difference between brown and red in this plot:
https://xe1t-wiki.lngs.infn.it/lib/exe/fetch.php?cache=&media=xenon:j_angevaare:n_photon_n_pe.png

Also see this thread:
https://xenonnt.slack.com/archives/C0177G05M1P/p1653034445289369

[JoranAngevaare]

As @zhut19 rightly pointed out the DAQ and hitfinder thresholds don't have to match one on one.

we could use the channel map to query the thresholds from the run-doc (something like Lutz example here:
https://github.com/XENONnT/corrections/issues/104).

I'm not entirely sure how much sense it makes to have different DAQ and hitfinder thresholds - especially if we use a fixed noise run. Changing the thresholds only really happens due to changing noise conditions. I'm curious what others think is best in this case?