Optionally add sync TPC reco mode

[shahor02]

DON'T merge yet.

TPC sync. reco. mode with clusters rejection is added is if ALIEN_JDL_DOTPCSYNCMODE=1 env.var. is defined. In this case, the original tpc-native-clusters.root file is used as an input to TPC sync. reco. and overwritten by it.

Still missing a possibility to complete --configKeyValues ... options of the sync.mode reco. by arbitrary settings passed via some JDL variable. @sawenzel , should we add to putConfigValues a new string argument which directly added to the options, w/o any parsing to key/values?

[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]

Thanks for this development. For what concerns the configuration of the task, could you provide an example of configKeyValue string that you would like to inject?

I am not a big fan of creating more and more JDL variables. Maybe we could try to adapt the existing mechanism of injecting configuration via json and the --overwrite-config mechanism. I'll just have to find a way to target injection in the level of tasknames. Should be doable.