CHG: Enclose all cout statements in g_Verbosity

[fhagemann]

Some cout statements were not enclosed in any g_Verbosity level statement, which should be fixed with this PR.

Or another side not: currently, when running with verbosity c_Info, the terminal gets flooded with output, mostly from the energy calibration printing every ADC to keV conversion. We might want to make use of the c_Chatty or c_Extreme verbosity levels from megalib also here in nuclearizer by moving some extreme output (especially that printed for EVERY strip hit) to c_Chatty or c_Extreme:

//! The global verbosity
extern int g_Verbosity;
// and its levels
extern const int c_Quiet;
extern const int c_Error;
extern const int c_Warning;
extern const int c_Info;
extern const int c_Chatty;
extern const int c_Extreme;

[ckierans]

Should we add e.g. "ERROR in src/MSubModuleShieldTrigger:ParseDeadtimeFile: " for the DEE submodules without the XmlTags, like you have for MSubModuleShieldTrigger?

[fhagemann]

I'm fine doing whatever for the DEE SubModules 😃
Should this be part of this PR or of a follow-up PR?

[ckierans]

Up to you, if you want to handle this in a follow-on PR, then I'd call this good to go once you rebase again.

[fhagemann]

Let's move this to a follow-up PR

[fhagemann]

I also see that this needs to be rebased, now that #194 was merged and this affects some files.

[fhagemann]

With the latest force-push, I am rebasing this onto the changes from #194 to enclose all cout statements in MModuleTACCalibration also in g_Verbosity.

See the two comments about using g_Warning, even though the error message says "Error"

[fhagemann]

This statement says Error, but it's being run for every MReadOutAssembly* Event and would spam the terminal output, that's why I chose c_Warning here.

[fhagemann]

This statement says Error, but it's being run for every MReadOutAssembly* Event and would spam the terminal output, that's why I chose c_Warning here.

[fhagemann]

I just rebased this.