Apply keys from generic config if applicable

[sawenzel]

Improvement for configuration: Apply the key-values from the generic config on top of the anchorConfig, if the anchorConfig does not have these keys themselves. Useful for key-values in the digitization space for instance since they are not mentioned in async reco workflows.

In addition, actually apply FT0DigParam and FV0DigParam to the digitization of FIT. This didn't have any effect so far.

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

Fixes an issue where FT0,FV0 were never applied in digitization despite intentions in this PR #1962

[sawenzel]

@shahor02 : Could you take a look if this is ok? I see that now we are also getting MFTAlpideParam which we never picked up before.

[shahor02]

@sawenzel looks fine, but what do you mean by MFTAlipedParam not used? It is loaded from the CCDB.