CI: putting back stronger constraints on TDD-5MHz tests

Signed-off-by: Raphael Defosseux <raphael.defosseux@eurecom.fr>

ci-scripts/xml_files/enb_usrp210_band40_test_05mhz_tm1.xml

@@ -65,7 +65,7 @@
                 <class>Ping</class>
                 <desc>ping (5MHz - 20 sec)</desc>
                 <ping_args>-c 20</ping_args>
-                <ping_packetloss_threshold>50</ping_packetloss_threshold>
+                <ping_packetloss_threshold>25</ping_packetloss_threshold>
         </testCase>
 
         <testCase id="040601">
@@ -112,7 +112,7 @@
 		<class>Iperf</class>
 		<desc>iperf (5MHz - UL/2Mbps/UDP)(30 sec)(unbalanced)</desc>
 		<iperf_args>-u -b 2M -t 30 -i 1 -R</iperf_args>
-		<iperf_packetloss_threshold>80</iperf_packetloss_threshold>
+		<iperf_packetloss_threshold>50</iperf_packetloss_threshold>
 		<iperf_profile>unbalanced</iperf_profile>
 	</testCase>
 

ci-scripts/xml_files/if4p5_usrp210_band40_test_05mhz.xml

@@ -81,7 +81,7 @@
                 <class>Ping</class>
                 <desc>ping (5MHz - 20 sec)</desc>
                 <ping_args>-c 20</ping_args>
-                <ping_packetloss_threshold>50</ping_packetloss_threshold>
+                <ping_packetloss_threshold>25</ping_packetloss_threshold>
         </testCase>
 
         <testCase id="040602">