Modify Lb2EtacKp lines to be the same as 2018-patches

Dear experts,

We would like to change the Lb2EtacKp lines to use the same configuration as 2018-patches, with the following changes:

(1) In the previous run1 stripping, the selections on protons are wrongly set to that of pions. This is fixed in 2018-patches.

(2) The name of the stripping in run1 contains two "Lb2EtacKp", and in 2018-patches there's only one, which is more consistent with other lines.

(3) We loosen the mass window of etac from 2.8GeV - 3.2GeV to 2.7GeV - 3.3GeV. This will be helpful when we fit the etac mass spectrum with a Lb mass constrain in the offline analysis.

(4) Change MDSTFlag to be 'False'

The rate has been tested using 50,000 test events of 2011 data, and 50,000 for 2012. Before the change, the rate is quite high, and the full log files are : log_50k_old_12 and log_50k_old_11; after the change, the rate is much lower, and the full log files are: log_50k_new12 and log_50k_new11.

The test result obtained using 2011 sample is:

StrippingReport                                                INFO Event 50000, Good event 50000
 |                                              *Decision name*|*Rate,%*|*Accepted*| *Mult*|*ms/evt*|
 |_StrippingGlobal_                                            |  0.0180|         9|       |   2.216|
 |_StrippingSequenceStreamBhadron_                             |  0.0180|         9|       |   2.200|
 |!StrippingLb2EtacKp_KsKPiLine                                |  0.0020|         1|  4.000|   1.264|
 |!StrippingLb2EtacKp_PPbarLine                                |  0.0000|         0|  0.000|   0.039|
 |!StrippingLb2EtacKp_4hLine                                   |  0.0180|         9|  3.333|   0.158|
 |!StrippingLb2EtacKp_KsKPiLine_TIMING                         |  0.0020|         1|  4.000|   0.033|
 |!StrippingLb2EtacKp_PPbarLine_TIMING                         |  0.0000|         0|  0.000|   0.033|
 |!StrippingLb2EtacKp_4hLine_TIMING                            |  0.0180|         9|  3.333|   0.034|

for 2012 sample it's:

StrippingReport                                                INFO Event 50000, Good event 50000
 |                                              *Decision name*|*Rate,%*|*Accepted*| *Mult*|*ms/evt*|
 |_StrippingGlobal_                                            |  0.1240|        62|       |   5.329|
 |_StrippingSequenceStreamBhadron_                             |  0.1240|        62|       |   5.309|
 |!StrippingLb2EtacKp_KsKPiLine                                |  0.0140|         7|  2.286|   3.511|
 |!StrippingLb2EtacKp_PPbarLine                                |  0.0000|         0|  0.000|   0.058|
 |!StrippingLb2EtacKp_4hLine                                   |  0.1140|        57|  2.737|   0.805|
 |!StrippingLb2EtacKp_KsKPiLine_TIMING                         |  0.0140|         7|  2.286|   0.043|
 |!StrippingLb2EtacKp_PPbarLine_TIMING                         |  0.0000|         0|  0.000|   0.036|
 |!StrippingLb2EtacKp_4hLine_TIMING                            |  0.1140|        57|  2.737|   0.047|

Both of them are low than the run2 case (see previous MR)

It is also observed that the 2011 rate is quite low due to some unknown reasons.