[ATR-22386] Integrate trigger doEDMVersionConversion into CA PHYS and PHYSLITE

This MR enables the flags.Trigger.doEDMVersionConversion to be functional in PHYS and PHYSLITE

It is only of relevance for derivations of Run 2 data and MC20.

This flag is still work in progress (it defaults to false) as the EDMVersionConversion procedure is not yet fully validated. Because of this

• The existing Run 2 matching data are not currently switched off if doEDMVersionConversion is true, but they should be once we're totally happy about this as otherwise we write the matching data twice. For Run 3 data/MC we've already reached this level of happiness.
• To aid with the validation, it is beneficial to have the full trigger output in PHYS. Hence it currently includes a single block of python which will get deleted down the line. This adds...
  • The converted HLTNav_R2ToR3Summary, this would ultimately be transient-only in the derivation job. But we can save it out for now to inspect it.
  • The full AODFULL Run 2 EDM (!) this is needed such that we have the HLT physics objects which are references from HLTNav_R2ToR3Summary

This adds ~50 kb event of data to PHYS, but to stress - this is only for testing!

Once HLTNav_R2ToR3Summary is produced, the R3 navigation slimming consumes it to produce HLTNav_Summary_DAODSlimmed and HLTNav_RepackedFeatures_Particle - this is the format which analysis should use. It will bring Run 2 data and MC20 in-line with Run 3 data, MC21 and MC23.

cc @wprzygod, @tbold, @jburr