MUST2 Thresholds (and resolutions) in npsimulation

Is there a reason why we fix the thresholds and the resolutions of the detectors in MUST2?

Suggestion: We can read the same MUST2 Config file to load the E-thresholds and use them in the simulation, this is important for efficiency calculations post experiment. Same can be said about the resolutions, new tokens (transparent for the analysis.cxx) can be added to the Config file to give the user more control on the E/T resolutions and avoid potential tampering with the source code.