Merge remote-tracking branch 'origin/nr_pdcch_demapping_deinterleaving-improve' into integration_2024_w39

Currently, NR PDCP ticks are active only with monolithic gNB, triggered by the MAC scheduler in gNB_scheduler.c.
In F1 split mode, as there is no MAC, there’s no source to advance the NR PDCP timer via "nr_pdcp_wakeup_timer_thread()".
This commit introduces a dedicated thread for NR PDCP ticks in gNB-CU and CU-UP mode.
Without it, packet losses at the F1 uplink would cause indefinite buffering, as t-Reordering won't expire due to the lack of NR PDCP timer ticks.

Fixing this avoids the theoretical possibility of dereferencing a NULL pointer.

Experiments did show that the time sync is less stable in terrestrial mode if the integral part of the PI controller is used.
So set it to 0.0 by default. For NTN LEO use case we can still use it by providing the command line parameter --time-sync-I 0.2 .
fixes #846

- Update builder dockerfiles to build Flexric for E2 SM
- Update target dockerfiles to copy E2 SM

	- correctly scale REs. Some REs have higher power during PDSCH RE-Mapping which is corrected.
	- Closes: Issue 811

- Add Jenkinsfile, triggering Colosseum test run
- Add test scripts that interact with Colosseum running

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

trigger RA DL or UL data arrival during RRC_CONNECTED when UL synchronisation status is non-synchronised