B23lnu: adapt RelInfoTools to have better ordering in MuonBDT
During the validation I noticed that my inclusive description for the MuonBDT RelInfo was not really helpful: the particles used for the MuonBDT were not ordered by type and thus a muon ID on e.g. electron/muon mixture was placed. Should be fixed now and tested on 100k events without any trouble. Tagging @alupato for the SL WG.
StrippingReport INFO Event 100000, Good event 100000
| *Decision name*|*Rate,%*|*Accepted*| *Mult*|*ms/evt*|
|!StrippingB23MuNu_TriMuLine | 0.0110| 11| 1.000| 5.554|
|!StrippingB23MuNu_TrieLine | 0.0220| 22| 1.000| 2.560|
|!StrippingB23MuNu_MueeLine | 0.0330| 33| 1.030| 0.207|
|!StrippingB23MuNu_MuMueLine | 0.0210| 21| 1.048| 0.084|
|!StrippingB23MuNu_TriFakeMuLine | 0.0090| 9| 1.333| 0.049|
|!StrippingB23MuNu_TrieFakeLine | 0.0050| 5| 1.000| 0.053|
|!StrippingB23MuNu_MuMueFakeLine | 0.0020| 2| 1.000| 0.047|
|!StrippingB23MuNu_MueeFakeLine | 0.0010| 1| 1.000| 0.038|
|!StrippingB23MuNu_TriMuLine_TIMING | 0.0110| 11| 1.000| 0.077|
|!StrippingB23MuNu_TrieLine_TIMING | 0.0220| 22| 1.000| 0.065|
|!StrippingB23MuNu_MueeLine_TIMING | 0.0330| 33| 1.030| 0.066|
|!StrippingB23MuNu_MuMueLine_TIMING | 0.0210| 21| 1.048| 0.061|
|!StrippingB23MuNu_TriFakeMuLine_TIMING | 0.0050| 5| 1.400| 0.037|
|!StrippingB23MuNu_TrieFakeLine_TIMING | 0.0030| 3| 1.667| 0.045|
|!StrippingB23MuNu_MuMueFakeLine_TIMING | 0.0120| 12| 1.417| 0.066|
|!StrippingB23MuNu_MueeFakeLine_TIMING | 0.0050| 5| 2.000| 0.044|