TauLRT chain development

This MR is to facilitate discussion and development on a new TauLRT chain setup.
We've added some initial TIDA plots in ATR-23787, which can also be used for further discussion
(or can do a separate ticket if it's for a specific issue)

We introduce the following trackLRT chain structure, comparing to the nominal tracktwoMVA chain:

"tracktwoMVA"   :['getCaloMVASeq',    'getFTFCore',  'getFTFIso'   , 'getPrecTrackIso' , 'getTrackTwoMVA' ],
"trackLRT"      :['getCaloMVASeq',    'getFTFLRT',   'getTrkEmpty' , 'getPrecTrackLRT' , 'getLRT' ],

   step                         task (→change)           RoI                     detail
----------------------------------------------------------------------------------------------------------------------------------------------------
1. Calo step: 		        L2 Fast Calo for Taus	 initialRoI		(untouched)
2. Tracking step: 		FTFCore → FTFLRT	 TauCore / TauLR         load LRT InDetConfig; update RoI (size 0.4/0.8 instead of 0.1/0.2)
3. Tracking/Iso step: 	        Iso / IsoBDT → Empty 	 TauIso			(no 2nd tracking step, ok without TrigTrackPreSelHypoAlg?)
4. Precision tracking step: 	PrecIso → PrecLRT	 			(duplicated) + load LRT InDetConfig 
5. ID step: 			MVA/MVABDT → LRT	 			scheduled LLP MVA, no other changes

.

Further details

• TauLRT tracking - InDet ConfigSettings.py
  Introduce HLT_Roi_TauLRT, zedHalfWidth to default 225.

• Update to ViewCreatorFetchFromViewROITool.cxx Allow resizing RoI through loading eta/phi/zed halfWidth, method taken from CentredOnClusterRoITool.

• Additions to TriggerEDMRun3.py
  Adding HLT_Roi_TauLRT, matching FTF and IDTrig tracking containers, a tau track container, and a TrigTauRec_LRT tau container.

• A number of test chains in Dev_pp_run3_v1.py

  • I added them with groups=DevGroup+['PS:NoHLTRepro'] as these shouldn't really run in general cases yet, but perhaps @gipezzul or @iriu can comment if there's a more appropriate menu config.

• Main LRT-case algorithm functions in TauRecoSequences.py

• Edits in TIDA setup to allow testing
  test_trigID_tauLRT_staustau.py should run, but ideally would replace the staustau RDO to use the d1735 or newer from a more recent trigger validation round (mc2X) (not in this MR)

• Ran standard trigger validation tests (ctest/runTrigART) without issues.

  • Updates ref_RDOtoRDOTrig_v1Dev_build.ref counts due to addition of new chains in dev menu, no changes in existing counts.

.

Thanks to @baines and @jgargan for helping to work out chain edits and a TIDA monitoring setup
and @ghamity and @gipezzul for the Tau signature documentation.
Tagging for info: @ghamity, @ademaria, @gipezzul, @iriu, @martindl