Allow TPC residual extraction in MC and data corr maps in the reco

[shahor02]

1. The TPC residuals extraction/aggregation is triggered by ALIEN_JDL_DOTPCRESIDUALEXTRACTION=1 env.var, as in the standard cpass. The only difference wrt cpass processing is that the calibration slot duration for the o2-tpc-scdcalib-interpolation-workflow is set to 1s (--sec-per-slot 1 ) to maximise the yield of tracks with residuals (virtually all tracks will be used).
   In opposite, the o2-calibration-residual-aggregator uses --sec-per-slot as in the original anchored workflow.

The output is o2tpc_residuals_<tsmin>_<tsmax>_<tfmin>_<tfmax>.root files.

2. if ALIEN_JDL_REMAPPINGS is defined, it will be applied as --condition-remap $ALIEN_JDL_REMAPPINGS added to all workflows supporting this option.

[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

[sawenzel]

Looks good. Would like to test it. Do I need a special run or should it work generically ?

[shahor02]

I've already tested it with the attached script, but want also to add/test a possibility to remap some CCDB objects to custom repositories (as for the planned test we will nee custom TPC correction maps).
xxx.tar.gz