DerivationFrameworkTau, tauRec, tauRecTools: optimise muon-tau removal sequence

DerivationFrameworkTau, tauRec, tauRecTools: optimise muon-tau removal sequence

Hello,

This MR is addressing the CPU increase in DAOD_PHYS/LITE reported in ATLASG-2712 coming from the recent addition of GNTau ID.
The main changes are in TauAODRunnerAlg, which first run a tool to remove muon tracks and clusters associated with tau candidate, then reruns most of the tau reconstruction with muon-free inputs.
Now, in the muon-tau removal, if no muon track nor cluster is found near the tau, we discard the tau candidate by effectively removing it from the container. This prevents afterburner tools like GNN tau ID from running over the full container (which so far includes irrelevant tau candidates removed later on by a thinning algorithm), thereby saving CPU. I've checked that the TauJets_MuonRM_TauIDDecorKernel CPU time is reduced, it's no longer visible in the SPOT test summary. The DAOD output is unchanged (checked over 1000 events).

Adding the urgent flag in case it would sill arrive in time for the imminent DAOD bulk prod.

Cheers,
Bertrand