Update of FIT digitizer parameters for 2025 data

[spulawsk]

This PR updates FT0 and FV0 digitizer settings for Run 3 data (runs 562260–568721) to better reflect 2025 conditions and recent digitizer improvements.

Key changes
FT0 calibration: set to ~14 ADC/MIP (mMip_in_V = 7, updated conversion factors)
System-dependent tuning:

• Pb–Pb: DCS-consistent FT0 thresholds and FV0 charge settings adapted to high multiplicity
• pp / OO / NeNe: DCS-consistent FT0 thresholds and FV0 charge levels for low-multiplicity systems
  FV0 ADC/MIP:
• pp: 15
• light systems (OO, NeNe, pO): 11

[github-actions]

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1
async-2024-PbPb-apass2
async-2023-PbPb-apass5

[spulawsk]

@jackal1-66 The error in the log seems to be related to MFT, so I do not think it comes from this PR.

[sawenzel]

@f3sch : It appears the ITS-MFT staggering development c9acd57adde in O2 breaks the O2DPG CI. The log says

3-[INFO] Init CcdApi with UserAgentID: o2-qc/o2-qc@12274 target/Linux_x86_64 init/1776652701146 id/mesosdaq@alimetal04.cern.ch session/YKqYhHT0, Host: http://alice-ccdb.cern.ch/(cache snapshots to dir=/sw/BUILD/f0a243902a4ac12198ccc818e8513d6b5b5273dc/O2DPG-sim-tests/o2dpg-sim_tests/o2dpg_tests/anchored/88_test_anchor_2023_apass2_pp.sh_dir/ccdb, prefer if available), Curl timeouts: upload:20 download:5
4-[INFO] CCDB Time-machine constrained detected. Setting condition-not-after constrained to timestamp 3385078236000
5-For later analysis we write a core dump to core_dump_12273
6:[FATAL] error while setting up workflow in o2-global-track-cluster-reader: missing option: enable-mft-staggering (No such node (enable-mft-staggering))
7-[ERROR] invalid workflow in o2-qc: No matching output found for <matcher query: (and origin:MFT (and description:CLUSTERSROF (and subSpec:0 (just startTime:$0 ))))> as requested by data processor "qc-task-MFT-Clusters". Candidates:

Do we need to change anything in O2DPG?