CA-tracking configuration per package: BackTracking + ConversionFinding
Now that the last discrepancies between legacy and new CA configs seem to have been ironed out, we had been discussing about the possibility to reorganise the structure of those to bring closer the different configurations of the same tools and algorithms. This should in particular make more clear what are their differences and hopefully help us understanding them better in some cases. This is expected to impact InDetConfig, TrkConfig, TrigInDetConfig and probably egammaConfig and MuonConfig.
The broad organising principle considered for this is to have one python config file per Athena package, having them in InDetConfig for the packages under InnerDetector or in TrkConfig for the packages under Tracking. A first example is available in the current draft MR.
Any feedback is very welcome on the general strategy proposed here.
This MR covers the configs used for BackTracking and ConversionFinding.
Draft will be lifted when agreement pre/post-MR is confirmed.