Sprucing lines hitting limit on number of passing combinations in ParticleCombiners

As shown in last weeks RTA-DPA meeting we have to impose a limit on the number of passing combinations in ParticleCombiners. Upon testing this the following combiners in SPRUCING lines hit this limit

B2CC_Kstar2KPi_WideRange_Filter_...    INFO Number of counters : 8
-- seems to be caused by the make_phi2kk combiner

B2OCB2DHHHCombiner_17d9789d            INFO Number of counters : 13
B2OCB2XCombiner_49c68c44               INFO Number of counters : 9 
B2OCB2XLooseMassMerger_668ecfe1        INFO Number of counters : 13
B2OCDst2D0PiCombiner_ebbac252          INFO Number of counters : 2
B2OCDstm2D0PimCombiner_20d31059        INFO Number of counters : 8
B2OCB2DHHHCombiner_17d9789d            INFO Number of counters : 1           
B2OCB2XCombiner_78940c92               INFO Number of counters : 11 
B2OCDst02D0Pi0Combiner_b91282cf        INFO Number of counters : 8 
B2OCDstp2D0PipCombiner_c217f17c....    INFO Number of counters : 1

make_rd_detached_K_1_1d722c7a          INFO Number of counters : 10
make_rd_detached_K_2_c3693410          INFO Number of counters : 10

make_detached_mue_with_brem_aa30...    INFO Number of counters : 1 
-- seems to be caused by the make_phi2kk combiner

The combiners used in HLT2 lines do not hit this limit and this only applies to Sprucing lines.

This will result in some inefficiency due to too loose combiners. The events run over here were not abnormally busy.

More info can be found in the MR

@abertoli @shunan @jzhuo @mfaria @oozcelik can you confirm you have seen this and tell us your plan?

Please note that no response will mean the combiners are kept as they are and the inefficiency will have to be dealt with by analysts