Introduce a new dumper for TauJets and associated TauTracks

Description

This MR is meant to provide an additional functionality to the TDD, useful in the context of GN2 usage for tau triggers. The main difference w.r.t. the workflow adopted for b-jet triggers is that trainings should also be done on TauJets (built out of LCTopo jets) and using tracks associated to those objects by the Tau reconstruction. For more details see e.g. here

The implementation contains the following ingredients:

• a new jet getter alg, TriggerTauJetGetter, which retrieves from the current chain a TauJetContainer, creates a corresponding JetContainer and attaches to that the tracks as linked to the TauJet object
• a new method in trigger.py, scheduling this getter and associating tracks from other useful track containers in the chain (two FTF and one Precision tracking containers, all being dumped with different names)
• a new executable, dump-trigger-tau, to actually run this option
• a new config file, trigger_tau.json, which configures this option
• additional track selection option fragments to avoid applying any track selection on tracks coming from the TauJet directly, apart from acceptance ones

This MR is meant for scrutinizing this option collectively as suggested by @dguest, so I am also happy to give a brief report introducing it at e.g. the next FTag SW meeting (@ligang and @robouque).

If and once accepted I will also add the corresponding documentation.

P.S: some extra work will be needed to add jet and track decorations to copy over extra TauJet and TauTrack info, and to save a cluster block as linked to the TauJet

Extra: this MR was discussed here