[TF3] Add efficiency, time resolution and ToA maps from ccdb

[GiorgioAlbertoLucia]

@maciacco

This pull request introduces improvements to the IOTOF digitizer simulation and a new macro to test the time resolution

Improvements in the digitization

• Added support in DPLDigitizerParam for specifying optional efficiency, resolution, and time of arrival map paths, which can be loaded from CCDB or various file sources

• Updated Digitizer to load these maps using a new loadMap method, supporting both CCDB and ROOT file sources, and to prepare a scaled resolution map for position-dependent time resolution

• The time smearing logic in Digitizer::smearTime now uses the loaded resolution and time of arrival maps to apply position-dependent Gaussian smearing

• NOTE: the resolution map determines the relative in-pixel resolution, while the nominal value is set by an independent parameter of the DPLDigitizerParam class

• Refactored map loading logic into a generic loadMap method and added prepareScaledResolutionMap for normalization, improving code maintainability and extensibility.

• Fixed a run-time inconsistency in the output size within IOTOFDigitizerSpec.cxx

Testing

• Added a new test macro CheckTimeResolutionIOTOF.C to the CMake configuration, ensuring that time resolution features can be tested and validated

Efficiency, time resolution and time of arrival maps can be found in the ccdb at these paths

• ccdb://Users/g/glucia/tmp/ALICE3/IOTOF/pixelEfficiency
• ccdb://Users/g/glucia/tmp/ALICE3/IOTOF/pixelResolution
• ccdb://Users/g/glucia/tmp/ALICE3/IOTOF/pixelTimeOfArrival

I will upload some examples of the mean and rms of the time resolution when the maps are used in the digitization
Input resolution map

Observed in-pixel resolution

Input time of arrival map

Observed in-pixel time of arrival

[maciacco]

Thanks Giorgio looks good to me. @njacazio this is ready to merge

[njacazio]

Good for me as well, let's see @shahor02

[shahor02]

Hi,
The proper way to load the ccdb object in the workflow is via DPL CCDB fetcher instead of the CCDB manager. If you need to make it conditional on the configurable option, this option simply should be checked the before making a request of the ccdb param e.g. here:

AliceO2/Steer/DigitizerWorkflow/src/IOTOFDigitizerSpec.cxx

Line 195 in fe47e4f

inputs.emplace_back("IOTOF_aptsresp", "TF3", "APTSRESP", 0, o2::framework::Lifetime::Condition, o2::framework::ccdbParamSpec("IT3/Calib/APTSResponse"));

.
That said, the case of loading a private file from the CCDB can also be handled via CCDB: one should just remap this particular CCDB object path to your private file linked to snapshot.root in the <path>/IT3/Calib/Smear via e.g.

--condition-remap file:///<path>=IT3/Calib/Smear"

I can merge this as is to not stall the work, but it would be good to fix this. Let me know.