Merge remote-tracking branch 'origin/extend-f1-ci-test' into integration_2025_w14_p2 (!3317)

Extend F1 Handover test

do 1 more handover in the same test to verify robustness

- This MR keeps a simple ping after the second handover since there are
  still issues due to scheduling starting too early, that is as soon as
  the UE context is added. This leads to retransmissions that could
  eventually lead to a test failure. The issue will be fixed in a future
  MR.

add check on connected DU to verify successful handover

- a new telnet function gets in input the UE ID and returns the ID of
  the connected DU

wait some time after deploying DU to mimic time for measurements

ci-scripts/xml_files/container_5g_f1_rfsim.xml

@@ -46,9 +46,15 @@
  020022
  040024
  000024
+ 000030
  040025
  000031
  030021
+ 040027
+ 040025
+ 000031
+ 020022
+ 040026
  100021
  222222
         </TestCaseRequestedList>
@@ -222,6 +228,22 @@
                 <command_fail>yes</command_fail>
         </testCase>
 
+        <testCase id="040026">
+                <class>Custom_Command</class>
+                <desc>UE (1) connected to DU-PCI 0?</desc>
+                <node>cacofonix</node>
+                <command>echo ci fetch_du_by_ue_id 1 | nc 192.168.71.150 9090 | grep "3584"</command>
+                <command_fail>yes</command_fail>
+        </testCase>
+
+        <testCase id="040027">
+                <class>Custom_Command</class>
+                <desc>UE (1) connected to DU-PCI 1?</desc>
+                <node>cacofonix</node>
+                <command>echo ci fetch_du_by_ue_id 1 | nc 192.168.71.150 9090 | grep "3585"</command>
+                <command_fail>yes</command_fail>
+        </testCase>
+
         <testCase id="100021">
                 <class>Undeploy_Object</class>
                 <always_exec>true</always_exec>